Well, to give M$ a little credit (duck), XP is supposed to have a fair
amount of security by default.
But, there's always that relationship between Security and Usability (is
that a word?).  I'm sure some
developers/admins will love the fact that they finally get to use Raw
Sockets, but that in turn decreases
some amount of security.  As people continue to add these new features, you
can't always an "Idiot Proofing" mechanism that works well...  It's a nice
double edged sword...
As for current windows machines, a million and one trojans already exist.
So my question is, is it the responsibly of the Vendor to make sure the
users know how to use a computer, or is it the responsibility of the user to
know how to use a computer?
As much as I love that certain vendor (sarcasm), their main focus is to put
out more productive products with a fair amount of security.  There aren't
enough resources in the world to make sure that every Joe Blow isn't leaving
themselves open...
My 2 cents...
Ricky
<p><p>-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of John Hebert
Sent: Tuesday, July 03, 2001 9:02 AM
To: [EMAIL PROTECTED]
Subject: Re: [brluglist] Fw: Steve Gibson's July/2001 News from GRC.COM
...
<p><p>--- Dustin Puryear <[EMAIL PROTECTED]> wrote:
<em>> Hmm. Is this about the raw socket deal with Windows
<em>> XP? Raw sockets have
<em>> been available in the UNIX world for a while, so I
<em>> guess that means UNIX
<em>> vendors are no better?
<em>>From my understanding of Gibson's writings, he says
that raw sockets are a problem in Windows XP because
most people use M$ Windows operating systems
(well, duh) AND M$ doesn't seem to have its act
together when it comes to network security (hmmm,
he's got a point). So, distributing M$ Windows XP
with raw sockets for home users who don't properly
secure their machines will only give DDOS script
kiddies more platforms to attack from.
:P
John
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/
================================================
BRLUG - The Baton Rouge Linux User Group
Visit http://www.brlug.net for more information.
Send email to [EMAIL PROTECTED] to change
your subscription information.
================================================
================================================
BRLUG - The Baton Rouge Linux User Group
Visit http://www.brlug.net for more information.
Send email to [EMAIL PROTECTED] to change
your subscription information.
================================================
<!-- body="end" -->
<hr noshade>
<ul>
<li><strong>Next message:</strong> Larry Braud: "Re: [brluglist] Fw: Steve 
Gibson's July/2001 News from GRC.COM ..."
<li><strong>Previous message:</strong> John Hebert: "Re: [brluglist] Fw: Steve 
Gibson's July/2001 News from GRC.COM ..."
<li><strong>In reply to:</strong> John Hebert: "Re: [brluglist] Fw: Steve 
Gibson's July/2001 News from GRC.COM ..."
<li><strong>Next in thread:</strong> Larry Braud: "Re: [brluglist] Fw: Steve 
Gibson's July/2001 News from GRC.COM ..."
<li><strong>Reply:</strong> Larry Braud: "Re: [brluglist] Fw: Steve Gibson's 
July/2001 News from GRC.COM ..."
<li><strong>Reply:</strong> john beamon: "RE: [brluglist] Fw: Steve Gibson's 
July/2001 News from GRC.COM ..."
<li><strong>Reply:</strong> Dustin Puryear: "Re: [brluglist] Fw: Steve Gibson's 
July/2001 News from GRC.COM ..."
<li><strong>Messages sorted by:</strong> 
[ date ]
[ thread ]
[ subject ]
[ author ]
[ attachment ]
</ul>
<hr noshade>

<small>
<em>
This archive was generated by hypermail 2.1.2 
: <em>Thu Sep 06 2001 - 11:10:53 CDT</em>
</em>
</small>
</body>
</html>

Reply via email to