From owner-freebsd-security@FreeBSD.ORG  Tue Sep  3 09:35:52 2013
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id C6209B4B
 for <freebsd-security@FreeBSD.org>; Tue,  3 Sep 2013 09:35:52 +0000 (UTC)
 (envelope-from slw@zxy.spb.ru)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
 by mx1.freebsd.org (Postfix) with ESMTP id 81AD32834
 for <freebsd-security@FreeBSD.org>; Tue,  3 Sep 2013 09:35:52 +0000 (UTC)
Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1VGn3d-000Fbd-0o; Tue, 03 Sep 2013 13:37:57 +0400
Date: Tue, 3 Sep 2013 13:37:57 +0400
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Dag-Erling Sm??rgrav <des@des.no>
Subject: Re: OpenSSH, PAM and kerberos
Message-ID: <20130903093756.GG3796@zxy.spb.ru>
References: <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> <86y57euu8y.fsf@nine.des.no>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <86y57euu8y.fsf@nine.des.no>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
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:35:52 -0000

On Tue, Sep 03, 2013 at 11:31:09AM +0200, Dag-Erling Sm??rgrav wrote:

> Slawa Olhovchenkov <slw@zxy.spb.ru> writes:
> > Dag-Erling Sm??rgrav <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.

And how in this case can be resolved situation with PAM credentials
(Kerberos credentials in may case)?