View Single Post
Old 19-10-2003, 15:19   #42
BBKing
R.I.P.
 
BBKing's Avatar
 
Join Date: Jun 2003
Location: London
Services: 20Mb VM CM, Virgin TV
Posts: 5,983
BBKing has a nice shiny starBBKing has a nice shiny starBBKing has a nice shiny starBBKing has a nice shiny starBBKing has a nice shiny star
BBKing has a nice shiny starBBKing has a nice shiny starBBKing has a nice shiny starBBKing has a nice shiny starBBKing has a nice shiny starBBKing has a nice shiny starBBKing has a nice shiny starBBKing has a nice shiny starBBKing has a nice shiny star
Send a message via ICQ to BBKing
Re: NTL to block port 135

They don't help themselves much though, I remember the Windows 2003 Server launch where the MS top brass trumpeted that it was written from the ground up with security in mind - can you say hostage to fortune? Needless to say, the first security hole followed shortly. Egg on the face all round.

2003 Server is a big improvement, though, in that practically anything interesting is turned off by default, which is a step forward. However, you won't see this on your own desktop for a bit, so XP SP2 is the next big upgrade, lets see what's in that from a security perspective.

Win2k/XP are being targetted now as they're getting more and more common (XP's been out nearly two years, so most modern PCs will be running it). Certainly anyone buying a new P4 PC (you need a P4 to make the internet work right, of course*) to connect to their new BB connection will have XP on it, and probably get infected straight off.

ntluser - the sad thing is that we'll fill the pockets of these guys whether or not they get it right, that's what they bank on. Going Open Source will really worry them though.

* this is irony
BBKing is offline   Reply With Quote