full-disclosure - openssh remote exploit

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: <3F6791B2.4080003@thievco.com>
From: BlueBoar at thievco.com (Blue Boar)
Subject: openssh remote exploit

Darren Reed wrote:
> No.  Does a vulnerability need an exploit before it becomes a hole ?

A programming error needs to be exploitable before it can be conclusively 
called a vulnerability or a hole.  One doesn't need to create an exploit 
for it to be exploitable, but it rather nicely answers the question, 
doesn't it?  It also often helps clarify what class of vulnerability it is.

None of which is news to you, you've been around a long time.  Are you 
baiting trolls or what?

					BB