RE: [Full-Disclosure] Re: Prudent default security
From: Schmehl, Paul L (pauls_at_utdallas.edu)
Date: 09/30/03
- Previous message: Florian Weimer: "Re: [Full-Disclosure] [OpenSSL Advisory] Vulnerabilities in ASN.1 parsing"
- Next in thread: Steve Wray: "RE: [Full-Disclosure] Re: Prudent default security"
- Reply: Steve Wray: "RE: [Full-Disclosure] Re: Prudent default security"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
To: "Full Disclosure" <full-disclosure@lists.netsys.com> Date: Tue, 30 Sep 2003 09:20:03 -0500
> -----Original Message-----
> From: Steve Wray [mailto:steve.wray@paradise.net.nz]
> Sent: Tuesday, September 30, 2003 4:58 AM
> To: 'Full Disclosure'
> Subject: RE: [Full-Disclosure] Re: Prudent default security -
> Was: CyberInsecurity: The cost of Monopoly
>
> I know that there are some nice tools for doing remote and bulk admin
> for the latest iterations of the Windows operating system,
> but from what I've seen, they lack maturity and often cause
> more trouble than they help prevent (DCOM? Am I right? Does
> anyone leave remote registry on?)
>
Steve, you should stop now. Your embarassing lack of knowledge of
Windows is all too obvious.
Paul Schmehl (pauls@utdallas.edu)
Adjunct Information Security Officer
The University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu/~pauls/
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html
- Previous message: Florian Weimer: "Re: [Full-Disclosure] [OpenSSL Advisory] Vulnerabilities in ASN.1 parsing"
- Next in thread: Steve Wray: "RE: [Full-Disclosure] Re: Prudent default security"
- Reply: Steve Wray: "RE: [Full-Disclosure] Re: Prudent default security"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
