From owner-freebsd-bugs@FreeBSD.ORG Sun Feb 1 05:46:49 2015 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A69D7757; Sun, 1 Feb 2015 05:46:49 +0000 (UTC) Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6EFB5791; Sun, 1 Feb 2015 05:46:49 +0000 (UTC) Received: by mail-oi0-f50.google.com with SMTP id h136so40340034oig.9; Sat, 31 Jan 2015 21:46:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=bXLSM8s3fQyBY0WhhNnP0uAbzNDdLY/1PKd42DidmaY=; b=K0+ONLnqUE3hFHaOFoWLCKEzG9ZfIn0yB9EApAJnGDrWDicKfZqD5i6Avh3G3umVF+ Gj4dr52D4pSLSpObpRzenNQkO94Ut7NET72GcEjGli2Z60VCIibux0vlywdN+qQLHuIm /QDIZ+evQkxF/4FefrPswMte4Hy8I+6UEp3+AgSjxye6ZZ0zPraNyWNXAXt05PF6/fbg GJ24iuTW0QKL87OVXv7ZmKpiQItCtfHIsPA4/D1eiJ/P5WBvxPYPOolnIGj69JqaHY1m 5C5C+/E1bCHBa6b9udaQvjbK/PjFiadVqIysybc1jZaFrD/Gr89gRRBj5QjHNWhdDf01 v2Cg== MIME-Version: 1.0 X-Received: by 10.182.104.42 with SMTP id gb10mr8267973obb.62.1422769608299; Sat, 31 Jan 2015 21:46:48 -0800 (PST) Received: by 10.76.29.37 with HTTP; Sat, 31 Jan 2015 21:46:48 -0800 (PST) Date: Sun, 1 Feb 2015 00:46:48 -0500 Message-ID: Subject: pam_krb5 broken From: Ansar Mohammed To: freebsd-bugs@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: gjb@freebsd.org X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Feb 2015 05:46:49 -0000 Hello There, I am testing the pam_krb5 module on FreeBSD 10.1. it seems that the code to save the Kerberos ticket on disk is broken. The call to pam_get_data in pam_sm_setcred is failing. As a result a user can login with Kerberos but running kinit does not show any cached tickets. I was reviewing the apple code here : http://www.opensource.apple.com/source/pam_modules/pam_modules-76/pam_krb5/pam_krb5.c and that appears insanely broken. I think they were also trying to fix the same error as they replaced pam_get_data/pam_set_data with pam_getenv/pam_setenv (but only halfway through the code)