Re: PAM OpenSSH 2.1 X11 - signal 11
On Fri, 2 Jun 2000, Hajimu UMEMOTO wrote: Thank you. It's working fine with wdm here. Good to know. BTW, I believe this version of pam_ssh.so doesn't support DSA key yet. Does someone working on it? Perhaps the author could tell us (CCed) :-) I'm on it. -- Andrew J. Korty, Lead Security Engineer Office of the Vice President for Information Technology Indiana University To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAM OpenSSH 2.1 X11 - signal 11
On Fri, 2 Jun 2000, Hajimu UMEMOTO wrote: BTW, I believe this version of pam_ssh.so doesn't support DSA key yet. Does someone working on it? Oops ... it looks like ssh-agent doesn't support DSA keys yet. Am I missing something? I suppose I could just add DSA support for the PAM authentication phase ... -- Andrew J. Korty, Lead Security Engineer Office of the Vice President for Information Technology Indiana University To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAM OpenSSH 2.1 X11 - signal 11
On Sun, 4 Jun 2000 12:30:42 -0500 (EST) "Andrew J. Korty" [EMAIL PROTECTED] said: On Fri, 2 Jun 2000, Hajimu UMEMOTO wrote: BTW, I believe this version of pam_ssh.so doesn't support DSA key yet. Does someone working on it? ajk Oops ... it looks like ssh-agent doesn't support DSA keys yet. Am ajk I missing something? I suppose I could just add DSA support for the ajk PAM authentication phase ... Oh, I see. You are right. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.imasy.org/~ume/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAM OpenSSH 2.1 X11 - signal 11
On Tue, 30 May 2000 12:30:41 -0700 (PDT) Kris Kennaway [EMAIL PROTECTED] said: kris On Tue, 30 May 2000, Alexander Leidinger wrote: I've just committed the version from ports to the source tree - could you verify it works? I have to wait until internat catches up, but I'm using pam_ssh.c from ports for a while and it didn't kill xdm. kris Oops, this is now committed to internat also. Thank you. It's working fine with wdm here. BTW, I believe this version of pam_ssh.so doesn't support DSA key yet. Does someone working on it? -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.imasy.org/~ume/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAM OpenSSH 2.1 X11 - signal 11
On Sun, 21 May 2000, Hajimu UMEMOTO wrote: 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've just committed the version from ports to the source tree - could you verify it works? Thanks, Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAM OpenSSH 2.1 X11 - signal 11
On 30 May, Kris Kennaway wrote: 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've just committed the version from ports to the source tree - could you verify it works? I have to wait until internat catches up, but I'm using pam_ssh.c from ports for a while and it didn't kill xdm. Bye, Alexander. -- Failure is not an option. It comes bundled with your Microsoft product. 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
Re: PAM OpenSSH 2.1 X11 - signal 11
On Tue, 30 May 2000, Alexander Leidinger wrote: I've just committed the version from ports to the source tree - could you verify it works? I have to wait until internat catches up, but I'm using pam_ssh.c from ports for a while and it didn't kill xdm. Oops, this is now committed to internat also. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAM OpenSSH 2.1 X11 - signal 11
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 2517, 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:
---snip---
(5) netchild@ttyp2% diff -duH /usr/src/crypto/openssh/pam_ssh/pam_ssh.c
/usr/ports/security/openssh/files/pam_ssh.c |wc
174 6715212
---snip---
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
[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.imasy.org/~ume/
Bye,
Alexander.
--
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
Re: PAM OpenSSH 2.1 X11 - signal 11
On Thu, 18 May 2000 16:19:25 +0200 (CEST)
Alexander Leidinger [EMAIL PROTECTED] said:
Alexander after a new build{world,kernel} after the import of OpenSSH 2.1 to
Alexander internat (cvsupped 2517, 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.
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.imasy.org/~ume/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
