full-disclosure - Re: Working exploit for Debian generated SSH Keys

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: <54606.1211298719@turing-police.cc.vt.edu>
Date: Tue, 20 May 2008 11:51:59 -0400
From: Valdis.Kletnieks@...edu
To: "Garrett M. Groff" <groffg@...design.com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: Working exploit for Debian generated SSH Keys

On Mon, 19 May 2008 13:51:29 EDT, "Garrett M. Groff" said:

> Generating pseudo-random numbers isn't hard given a good API, but writing
> that API is non-trivial (assuming you want high entropy/low
> predictability). And, apparently, screwing up that API is also very easy.

Of course, if you're trying to write a PoC, you don't need to know how to
code the API - all you need to do is grab the source for the key-tester that
got shipped as part of the OpenSSH patch and snarf out the nicely enumerated
list of all vulnerable keys, and use that list as the brute-forcer, 6 per
connection attempt. ;)

Content of type "application/pgp-signature" skipped

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