> 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
> 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 aut
> 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
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) :-)
Kris
--
In God we Trust -- all others must
> 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
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 t
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 - c
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
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 th
> 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
10 matches
Mail list logo
