full-disclosure - re: openssh exploit code?

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] [day] [month] [year] [list]

From: smcmahon at eiv.com (Shawn McMahon)
Subject: re: openssh exploit code?

Frank Knobbe wrote:
> 
> heh... Nothing wrong with that statement. However, the severity of the
> issue (DoS vs. remote-root) would be helpful in determining if admins
> should yank the boxes during production, or wait to patch after hours.

Especially if one has boxes for which "after hours" is "once a quarter"
or "never".

I've got projects with both.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: file:///tmp/nsmail.tmp
Type: application/pgp-signature
Size: 252 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20031020/fb89e906/nsmail.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 252 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20031020/fb89e906/attachment.bin