On Fri, Aug 30, 2013 at 02:51:44PM +0200, Dag-Erling Sm??rgrav wrote:
> Slawa Olhovchenkov writes:
> > Dag-Erling Sm??rgrav writes:
> > > PAM authentication in OpenSSH was broken for non-trivial cases when
> > > privilege separation was implemented. Fixing it properly would be
> > > very diffic
Slawa Olhovchenkov writes:
> Dag-Erling Smørgrav writes:
> > PAM authentication in OpenSSH was broken for non-trivial cases when
> > privilege separation was implemented. Fixing it properly would be
> > very difficult.
> Same behaviour with 'UsePrivilegeSeparation no'. This issuse not in
> priv
On Fri, Aug 30, 2013 at 02:09:26PM +0400, Slawa Olhovchenkov wrote:
> On Fri, Aug 30, 2013 at 09:44:54AM +0200, Dag-Erling Sm??rgrav wrote:
>
> > Slawa Olhovchenkov writes:
> > > I am try to setup single sign-on and found this is imposuble due to
> > > bug in OpenSSH: currently sshd do pam_authe
On Fri, Aug 30, 2013 at 09:44:54AM +0200, Dag-Erling Sm??rgrav wrote:
> Slawa Olhovchenkov writes:
> > I am try to setup single sign-on and found this is imposuble due to
> > bug in OpenSSH: currently sshd do pam_authenticate() and
> > pam_acct_mgmt() from child process, but pam_setcred() from pa
Slawa Olhovchenkov writes:
> I am try to setup single sign-on and found this is imposuble due to
> bug in OpenSSH: currently sshd do pam_authenticate() and
> pam_acct_mgmt() from child process, but pam_setcred() from paren
> proccess. pam_krb5 in pam_sm_setcred() required information from
> pam_sm
