From owner-freebsd-bugs@freebsd.org  Thu Dec 17 20:25:10 2015
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8D0DEA4AAC8
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Thu, 17 Dec 2015 20:25:10 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 7D63B189B
 for <freebsd-bugs@FreeBSD.org>; Thu, 17 Dec 2015 20:25:10 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tBHKPAYY072513
 for <freebsd-bugs@FreeBSD.org>; Thu, 17 Dec 2015 20:25:10 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 107154] [pam] pam.d/sshd pam_ssh.so doesn't start ssh-agent
Date: Thu, 17 Dec 2015 20:25:10 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 6.2-PRERELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: des@FreeBSD.org
X-Bugzilla-Status: Closed
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_status resolution cc
Message-ID: <bug-107154-8-TyB6dpcknk@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-107154-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-107154-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Dec 2015 20:25:10 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D107154

Dag-Erling Sm=C3=83=C2=B8rgrav <des@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|In Progress                 |Closed
         Resolution|---                         |Rejected
                 CC|                            |des@FreeBSD.org

--- Comment #1 from Dag-Erling Sm=C3=83=C2=B8rgrav <des@FreeBSD.org> ---
This is specific to sshd.  It runs pam_open_session(3) in a different proce=
ss
than pam_authenticate(3), so the SSH key that pam_ssh(8) loaded and decrypt=
ed
while executing the latter is not available when executing the former.  Thi=
s is
a
fundamental flaw in (depending on who you ask) PAM, OpenSSH, or the way PAM=
 is
integrated into OpenSSH.

--=20
You are receiving this mail because:
You are the assignee for the bug.=