full-disclosure - MS should point windowsupdate.com to 127.0.0.1

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

Message-ID: <871080DEC5874D41B4E3AFC5C400611E03F607C4@UTDEVS02.campus.ad.utdallas.edu>
From: pauls at utdallas.edu (Schmehl, Paul L)
Subject: MS should point windowsupdate.com to 127.0.0.1

> -----Original Message-----
> From: Jeremiah Cornelius [mailto:jeremiah@....net] 
> Sent: Friday, August 15, 2003 12:34 PM
> To: Schmehl, Paul L
> Cc: full-disclosure@...ts.netsys.com
> Subject: Re: [Full-Disclosure] MS should point 
> windowsupdate.com to 127.0.0.1
> 
> Paul,
> Yours was EXACTLY the scenario for which HOGWASH - a 
> filtering proxy based on snort - was written.  The hogwash 
> project was eventually due to be folded back into the 
> mainline snort code base.  I don't know if this has happened yet.
> 
http://hogwash.sourceforge.net/docs/overview.html

I'm aware of that.  I use snort here.  I didn't provide *all* the
details of this scenario, because the point wasn't to solicit a
solution, but to present a dilemma to the know-it-alls and see whether
they had even considered any alternatives.

At any rate, love snort, love open source, gentoo rules, microsoft
sucks, hoo rah and all that good stuff.

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