“If you have just finally finished figuring out the relationship between the various versions of operating systems coming out from Microsoft over the past couple of years, get ready to be challenged once again. The successor line to the server versions of the Windows 2000 operating system is called .NET Server and is currently available as a Beta 3 release to MSDN subscribers and other beta testers. It was originally called Whistler Server, but after the Beta 2 release it acquired a new name (despite an interim announcement that Whistler Server would be released as Windows 2002 Server). In this article I’ll try to summarize what is new and exciting in this new release.” Read the article at O’Reilly.
Previewing Windows .NET Servers
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
“Windows .NET Web Server
This is a new version that does not correspond to any version of the Windows 2000 line of operating systems. It is meant to be used as a dedicated Web server for hosting applications and Web services. Since this is the low-end configuration of the .NET Server, it is limited to servers with either one or two CPUs and up to 2GB of RAM”
well, at least now you will have a dedicated product that you can disconect from the network when it gets hit by a nimbda like worm 🙂
“well, at least now you will have a dedicated product that you can disconect from the network when it gets hit by a nimbda like worm :-)”
Just like when a linux box when it gets rooted?
since you have to make a concerted effort to root a linux server, you can’t make a stupid little worm like Nimbda since for code to be executed, it must have the X permission turned on…how is a program gong to turn on the X bit to execute it self so it can gain root access when you need root access to turn on the X bit?
hmmm just won’t work.
It’s more like the worm that went around briefly when BIND was found rootable awhile back. There was a kit that, scanned, rooted, and installed backdoors. The difference is that Linux people tend to pay more attention, so it wasn’t as widespread.
I remember that the Ramen worm was pretty nasty but I don’t know exactly how many Linux servers it infested (lots). Ramen got plenty of fame and attention at the time (and it wasn’t all that long ago, either).
Of course, anyone old enough to remember the Morris worm of 1988 (that virtually shut down the entire internet for a week) knows that Unix has always had just as many holes as anything else for hackers to jump through (except for OpenBSD).
Why is it always .NET here and never J2EE?
Here is a good start: http://www.theserverside.com
Why I use OpenBSD religiously.
.
http://wire.ap.org/APnews/main.html?SLUG=OBIT%2dBONANNO>NoTo…
little billygates, aka donfuddles, aka billy the FUDgePacker, aka billy the .con, is rumoured to be still aLIEv/livid, & so far, avoiding ANY penaltIEs for his alleged crimes, while planning even more ill eagle behaviours, heis, IT is rumoured, buy condition of anonymity, couNTing (literally) on the .continued $support$/encouragemeNT of the once powerful (now a BiG joke in the KingDumb) US gov’t.. “family”, aka the lamo brothers, aka georgIE’s bouys.