One of many such concerns:
Windows XP Home Edition
Must be Made More Secure
Page last modified: Aug 31, 2001 at 14:37 by Steve Gibson
TechTV asked me to briefly explain my concerns
about Windows XP and its threatened support
for unrestricted full raw sockets.
Playing Time: 4 min. (See Media page for help)
WMV Video: 6.7 MB MP3 Audio: 0.9 MB
(Right Click on the link to SAVE the file before viewing.)
I believe that Microsoft and I have been locked
in a misunderstanding. But it is one that is too
important to ignore . . . and not too late to fix!
Due to a misunderstanding right from the start, Microsoft and I have been talking about different issues relating to raw sockets: I have been saying that raw sockets are not necessary and are dangerous, while Microsoft has been saying that they are necessary and are no more dangerous than alternatives.
Each of us, from our perspective, has been
correct, but we have been talking about
different aspects of raw sockets.
I have been talking about USER access to raw sockets being dangerous and unnecessary, while Microsoft has been talking about SYSTEM access to raw sockets being necessary, and no more dangerous than other networking technologies available in the system.
What's so odd about this . . . is that we agree with each other!
Please take a look at this page containing excerpts from Microsoft's own current web pages explaining how all access to raw sockets is deliberately restricted to administrative users.
It is clear that raw sockets are not necessary for typical personal computer users, and that Microsoft themselves never intended common users to have them. This is in keeping with traditional industry-wide support for the Berkeley raw socket interface.
Ask yourself this: If the raw socket interface, originated at U.C. Berkeley 20 years ago, were not a security risk for users, for systems, and for the Internet, then WHY has this interface always been restricted from casual use everywhere it has ever appeared?
I have NO PROBLEM with RESTRICTED access to the raw socket interface, and no problem with the SYSTEM having access to the interface. That is traditionally what has always been done on Unix, Linux, and similar systems and, as we have seen on Microsoft's own pages, in Windows.
But HERE is what has suddenly changed:
Under the Home Edition of Windows XP,
ALL users are Administrators by default.
Microsoft's reasons for doing this are clear, reasonable, and understandable: Many Windows 9x/ME legacy applications would fail to operate within an environment that suddenly imposes security restrictions. Microsoft's solution to this for Windows XP has been to run all users in the system as administrators.
For much more detailed information of the problem, read the article at:
http://<font color=blue>http://grc.com/dos/winxp.htm</font color=blue> As previously stated, there are many such reviews on different techie boards. All pointing to the fact of XP's being an open portal to your computer. While some may maintain XP's security is the best since..... I will not take that stance, until this area at least is taken out of XP common user access.
<P ID="edit"><FONT SIZE=-1>
Edited by scruffy on 10/21/01 11:53 AM (server time).</FONT></P>