"David O'Brien" <[EMAIL PROTECTED]> writes:
> so getting an OPIE formatted challenge on RELENG_4 immediately lets
> someone know it is fake and bogus.
I know. I told you it is a bug in the server.
> > the client attempts challenge-response authentication, which is what
> > is used for PAM.
> I
On Tue, Apr 02, 2002 at 01:48:56AM +0200, Dag-Erling Smorgrav wrote:
> "David O'Brien" <[EMAIL PROTECTED]> writes:
> > On Sat, Mar 30, 2002 at 01:14:07PM +0100, Dag-Erling Smorgrav wrote:
> > > "David O'Brien" <[EMAIL PROTECTED]> writes:
> > > > Uh, why does my sequence keep changing when I just h
"David O'Brien" <[EMAIL PROTECTED]> writes:
> On Sat, Mar 30, 2002 at 01:14:07PM +0100, Dag-Erling Smorgrav wrote:
> > "David O'Brien" <[EMAIL PROTECTED]> writes:
> > > Uh, why does my sequence keep changing when I just hit ???
> > Because it's generating fake S/Key challenges, and badly.
> Especi
On Sat, Mar 30, 2002 at 01:14:07PM +0100, Dag-Erling Smorgrav wrote:
> "David O'Brien" <[EMAIL PROTECTED]> writes:
> > Something is still very wrong:
> >
> > ssh foo@releng4
> > otp-md5 350 re9786 ext
> > S/Key Password:
> > otp-md5 134 re2584 ext
> > S/Key Password:
> >
"David O'Brien" <[EMAIL PROTECTED]> writes:
> Something is still very wrong:
>
> ssh foo@releng4
> otp-md5 350 re9786 ext
> S/Key Password:
> otp-md5 134 re2584 ext
> S/Key Password:
> otp-md5 417 re5381 ext
> S/Key Password:
> otp-md5 198 re2571 ext
> S/Ke
On Fri, Mar 29, 2002 at 11:01:25AM +0100, Thomas Quinot wrote:
> Le 2002-03-29, Will Andrews écrivait :
>
> > SSH should just be fixed to DTRT when one doesn't have S/Key
> > setup on the server...
>
> As far as I can understand the sources, this has been implemented
> in rev. 1.10 of src/crypto
Le 2002-03-29, Will Andrews écrivait :
> SSH should just be fixed to DTRT when one doesn't have S/Key
> setup on the server...
As far as I can understand the sources, this has been implemented
in rev. 1.10 of src/crypto/openssh/auth-skey.c.
Thomas.
--
[EMAIL PROTECTED]
To Unsubscribe: se
hi, there!
On Thu, Mar 28, 2002 at 11:43:58AM -0800, Julian Elischer wrote:
> > On Thursday 28 March 2002 10:28 am, Michael L. Hostbaek wrote:
> > > Beech Rintoul (akbeech) writes:
> > >
> > > 'ChallengeResponseAuthentication no'
> >
> > Thanks, that fixed the problem.
>
> just stops my sshd f
On Thu, Mar 28, 2002 at 12:03:17PM -0800, David O'Brien wrote:
> That is NOT a fix. Some of us want S/Key (OPIE) support.
> This is a temperary work around.
And some of us want passphrase support. :-)
SSH should just be fixed to DTRT when one doesn't have S/Key
setup on the server... however, i
* David O'Brien <[EMAIL PROTECTED]> [2002-03-28 21:06]:
> On Thu, Mar 28, 2002 at 10:40:04AM -0900, Beech Rintoul wrote:
> > > > #ssh -l akbeech galaxy
> > > > #otp-md5 336 ga3711 ext
> > > > S/Key Password:
> > >
> > > Adding the following setting to sshd_config, should disable S/Key
> > > functi
On Thu, Mar 28, 2002 at 10:40:04AM -0900, Beech Rintoul wrote:
> > > #ssh -l akbeech galaxy
> > > #otp-md5 336 ga3711 ext
> > > S/Key Password:
> >
> > Adding the following setting to sshd_config, should disable S/Key
> > functionality:
> >
> > 'ChallengeResponseAuthentication no'
>
> Thanks, tha
On Thu, 28 Mar 2002, Beech Rintoul wrote:
> On Thursday 28 March 2002 10:28 am, Michael L. Hostbaek wrote:
> > Beech Rintoul (akbeech) writes:
> >
> > 'ChallengeResponseAuthentication no'
>
> Thanks, that fixed the problem.
just stops my sshd from working at all.
(machine is 4.1.1)
To Uns
Beech Rintoul wrote:
> I just updated -current (yesterday) and now I'm getting the following when I
> try to use ssh:
>
> #ssh -l akbeech galaxy
> #otp-md5 336 ga3711 ext
> S/Key Password:
>
> Any suggestions?
Downgrade, and submit a reverse diff to back out whatever
change was made that's urin
On Thursday 28 March 2002 10:28 am, Michael L. Hostbaek wrote:
> Beech Rintoul (akbeech) writes:
> > I just updated -current (yesterday) and now I'm getting the following
> > when I try to use ssh:
> >
> > #ssh -l akbeech galaxy
> > #otp-md5 336 ga3711 ext
> > S/Key Password:
>
> Adding the follow
Beech Rintoul (akbeech) writes:
> I just updated -current (yesterday) and now I'm getting the following when I
> try to use ssh:
>
> #ssh -l akbeech galaxy
> #otp-md5 336 ga3711 ext
> S/Key Password:
>
Adding the following setting to sshd_config, should disable S/Key
functionality:
'Challeng
On Thu, Mar 28, 2002 at 09:37:36AM -0900, Beech Rintoul wrote:
> I just updated -current (yesterday) and now I'm getting the following when I
> try to use ssh:
>
> #ssh -l akbeech galaxy
> #otp-md5 336 ga3711 ext
> S/Key Password:
>
> Any suggestions?
hit any set of letters until you get a r
I just updated -current (yesterday) and now I'm getting the following when I
try to use ssh:
#ssh -l akbeech galaxy
#otp-md5 336 ga3711 ext
S/Key Password:
Any suggestions?
Beech
--
---
Beech Rintoul - IT Manager - Instructor -
Great ... I added RANDOMDEV to the wrong kernel config file :(
Thanks, fixed now ...
On Fri, 21 Jul 2000, Alexander Langer wrote:
> Thus spake The Hermit Hacker ([EMAIL PROTECTED]):
>
> > Just upgraded to the newest -current, and now can't use SSH:
> > ssh: no RSA support in libssl and lib
Thus spake The Hermit Hacker ([EMAIL PROTECTED]):
> Just upgraded to the newest -current, and now can't use SSH:
> ssh: no RSA support in libssl and libcrypto. See ssl(8).
options RANDOMDEV into kernel, or load randomdev.ko
That solved it for me (though you mentioned it).
I'M USA_RESIDENT=NO,
Hi
I had the same problem ... but in my case I did not have the
RANDOMDEV compiled in ... so I loaded the kld and whala ... it
worked ...
Try loading the KLD .. also check that the lib's actually do
include the RSA stuff (nm | grep RSA ) might help.
Reinier
On 21-Jul-00 The Hermit Hacker w
Just upgraded to the newest -current, and now can't use SSH:
ssh: no RSA support in libssl and libcrypto. See ssl(8).
Tried to read the 'ssl(8)' man page, but it comes back as:
> man 8 ssl
No entry for ssl in section 8 of the manual
> man ssl
No manual entry for ssl
>
Did mergemaster and saw
21 matches
Mail list logo
