On 21 May, Hajimu UMEMOTO wrote:

[kris CCed, I think hi knows how to handle this]

> Alexander> after a new build{world,kernel} after the import of OpenSSH 2.1 to
> Alexander> internat (cvsupped 20000517, around 14:00 CEST), xdm gets a signal
> Alexander> 11 if I use pam_ssh.so (after entering the password).
> Alexander> After removing the lines with pam_ssh.so for xdm I'm able to login.
> Alexander> Is someone else able to reproduce this?
> I also met this with wdm here.
> To avoid this problem, I replaced pam_ssh.c with
> ports/security/opessh/pam_ssh.c with changing PATH_SSH_AGENT to
> /usr/bin/ssh-agent.  It seems working.

I haven't tried it (yet), but a diff between both (src/crypto/... and
ports/...) show many differences:
(5) netchild@ttyp2% diff -duH /usr/src/crypto/openssh/pam_ssh/pam_ssh.c 
/usr/ports/security/openssh/files/pam_ssh.c |wc 
     174     671    5212

Some of them are ok (__PREFIX__), but the other differences are changes
to support DSA-keys (if I read this correctly).

Kris, may I assume they get merged into the tree soon?

> --
    ^ It seems you have forgotten to add a space after the dashes.
> Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
> http://www.imasy.org/~ume/


               I believe the technical term is "Oops!"

http://www.Leidinger.net                  Alexander+Home @ Leidinger.net
  GPG fingerprint = 7423 F3E6 3A7E B334 A9CC  B10A 1F5F 130A A638 6E7E

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to