From owner-freebsd-security@FreeBSD.ORG  Tue Sep  3 09:31:09 2013
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id AD12393D
 for <freebsd-security@FreeBSD.org>; Tue,  3 Sep 2013 09:31:09 +0000 (UTC)
 (envelope-from des@des.no)
Received: from smtp.des.no (smtp.des.no [194.63.250.102])
 by mx1.freebsd.org (Postfix) with ESMTP id 6D07C2787
 for <freebsd-security@FreeBSD.org>; Tue,  3 Sep 2013 09:31:09 +0000 (UTC)
Received: from nine.des.no (smtp.des.no [194.63.250.102])
 by smtp-int.des.no (Postfix) with ESMTP id 6FE364266;
 Tue,  3 Sep 2013 09:31:08 +0000 (UTC)
Received: by nine.des.no (Postfix, from userid 1001)
 id 7474E339AF; Tue,  3 Sep 2013 11:31:09 +0200 (CEST)
From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>
To: Slawa Olhovchenkov <slw@zxy.spb.ru>
Subject: Re: OpenSSH, PAM and kerberos
References: <20130829004844.GA70584@zxy.spb.ru> <86d2ovy64p.fsf@nine.des.no>
 <20130830100926.GU3796@zxy.spb.ru> <20130830103009.GV3796@zxy.spb.ru>
 <86sixrwdcv.fsf@nine.des.no> <20130830131455.GW3796@zxy.spb.ru>
 <8661uj9lc6.fsf@nine.des.no> <20130902181754.GD3796@zxy.spb.ru>
 <867geywdfc.fsf@nine.des.no> <20130903083301.GF3796@zxy.spb.ru>
Date: Tue, 03 Sep 2013 11:31:09 +0200
In-Reply-To: <20130903083301.GF3796@zxy.spb.ru> (Slawa Olhovchenkov's message
 of "Tue, 3 Sep 2013 12:33:01 +0400")
Message-ID: <86y57euu8y.fsf@nine.des.no>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-security@FreeBSD.org
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Sep 2013 09:31:09 -0000

Slawa Olhovchenkov <slw@zxy.spb.ru> writes:
> Dag-Erling Sm=C3=B8rgrav <des@des.no> writes:
> > The proper solution would be an identification and authentication daemon
> > with a well-designed RPC interface and mechanisms for transferring
> > environment variables, descriptors and credentials from the daemon to
> > the application (in this case, sshd).
> I think this is impossible, because credentials for pam_krb5 is simple
> pointer to internal blob's with unknown size, structure and links with
> other elements.

When I spoke of passing credentials, I meant process credentials, not
the cached Kerberos credentials - which the application does not need
anyway.  See SCM_CREDS in recv(2) for further information.

DES
--=20
Dag-Erling Sm=C3=B8rgrav - des@des.no