full-disclosure - No Subject (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]

Message-ID: <Pine.LNX.4.44.0310211134330.23145-100000@kepler.acns.bethel.edu>
From: b-nordquist at bethel.edu (Brent J. Nordquist)
Subject: No Subject (re: openssh exploit code?)

On Tue, 21 Oct 2003, Schmehl, Paul L <pauls@...allas.edu> wrote:

> I personally would prefer that every system gets patched the day the
> patch is released.

I wouldn't.  What happens when the patch is broken?  But that's just one
more factor to consider, underneath your larger argument:  "in the real
world, decisions about taking critical systems down are based on a number
of factors"... and with that, I agree 100%.  This list's main value to me
is adding more data to be weighed in making those decisions.

-- 
Brent J. Nordquist <b-nordquist@...hel.edu> N0BJN
Other contact information: http://kepler.acns.bethel.edu/~bjn/contact.html
* Fast pipe * Always on * Get out of the way - Tim Bray http://tinyurl.com/7sti