full-disclosure - Re: OpenSSH - System Account Enumeration if S/Key is used

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <242a0a8f0704240706j52cbdad9i1626678704121755@mail.gmail.com>
Date: Tue, 24 Apr 2007 10:06:58 -0400
From: "Brian Eaton" <eaton.lists@...il.com>
To: "Stanislaw Klekot" <dozzie@...amit.im.pwr.wroc.pl>
Cc: full-disclosure@...ts.grok.org.uk, rembrandt <rembrandt@...ith.org>
Subject: Re: OpenSSH - System Account Enumeration if S/Key
	is used

On 4/24/07, Stanislaw Klekot <dozzie@...amit.im.pwr.wroc.pl> wrote:
> Look closer to challenge message. There's salt and key number included.
> Consider now three logins: first isn't valid account on the target
> system, second is valid but without OTP set, and third with OTP set.
> First two are indistinguishable for attacker as in these cases system
> presents random challenge, but for third account system will present the
> same challenge over and over again.
>
> How about that?

Perhaps rather than presenting a random challenge, the challenge could
be based on a hash of the account name used and a per-system salt?

Regards,
Brian

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/