|
|
BugTraq
OpenSSH/PAM timing attack allows remote users identification Apr 30 2003 02:34PM Marco Ivaldi (raptor mediaservice net) (4 replies) Re: OpenSSH/PAM timing attack allows remote users identification May 02 2003 01:15PM Michael Shigorin (mike osdn org ua) (1 replies) Re: OpenSSH/PAM timing attack allows remote users identification May 02 2003 01:48PM Marco Ivaldi (raptor mediaservice net) Re: OpenSSH/PAM timing attack allows remote users identification May 02 2003 12:56AM Karl-Heinz Haag (k haag linux-ag com) Re: OpenSSH/PAM timing attack allows remote users identification May 01 2003 03:20PM Thilo Schulz (arny ats s bawue de) (1 replies) Re: OpenSSH/PAM timing attack allows remote users identification May 02 2003 11:20AM Marco Ivaldi (raptor mediaservice net) |
|
Privacy Statement |
> root@voodoo:~# ssh [valid_user]@lab.mediaservice.net
> [valid_user]@lab.mediaservice.net's password: <- arbitrary (non-null) string
> [2 secs delay]
> Permission denied, please try again.
>
> root@voodoo:~# ssh [no_such_user]@lab.mediaservice.net
> [no_such_user]@lab.mediaservice.net's password: <- arbitrary (non-null) string
> [no delay]
> Permission denied, please try again.
ive noticed something similar in its handling of PermitRootLogin, if
this option is set to `no' you get the following behavior:
$ ssh root@host
root@host's password: <- arbitrary (non-null) string
[2 secs delay]
Permission denied, please try again.a
$ ssh root@host
root@host's password: <- correct root password
[no delay]
Permission denied, please try again.
i haven't checked the current version to see if this is still true.
i think you also will get no delay if DenyUsers or so is in use for
accounts your testing.
--
Ethan Benson
http://www.alaska.net/~erbenson/
[ reply ]