full-disclosure - RE: W2K source "leaked"?

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

Message-ID: <15533237421C6E4296CC33A2090B224A54CBA2@UTDEVS02.campus.ad.utdallas.edu>
From: pauls at utdallas.edu (Schmehl, Paul L)
Subject: RE: W2K source "leaked"?

> -----Original Message-----
> From: full-disclosure-admin@...ts.netsys.com 
> [mailto:full-disclosure-admin@...ts.netsys.com] On Behalf Of 
> Joe Quigley
> Sent: Friday, February 13, 2004 11:00 AM
> To: Drew Copley; Gadi Evron; bugtraq@...urityfocus.com
> Cc: full-disclosure@...ts.netsys.com
> Subject: [Full-Disclosure] RE: W2K source "leaked"?
> 
> 
> Drew Copley once said:
> 
> > We should prepare for this now.
> 
> Anyone care to comment how we can prepare for this?? Except 
> for moving from the Windows platform, I don't see how we can. 
> Please do not take this as knock against Drew and his 
> opinion. It most certainly isn't. I really would like to hear 
> others thoughts on this.
>
Odd.  I would have thought the answer was self evident.  You take the
standard precautions that every security person should know. Shut down
unnecessary services, block all incoming ports except those services
necessary to function, create secure "areas" within which you keep the
"crown jewels", develop a consistent, effective program of patching,
security awareness, yada, yada, yada, etc., etc., etc.

Paul Schmehl (pauls@...allas.edu)
Adjunct Information Security Officer
The University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu/~pauls/