I was amused by your claims that a)SP3 is free and b)that by not installing it, you lose nothing.
Considering the licensing requirements of SP3 can put a compliant company on the wrong side of the law (1, 2) I would not consider it to be free (in any sense of the term). But considering the number of problems/issues that SP3 supposedly addresses (in the areas of "application compatibility, operating system reliability, security, and setup"), leaving your system as is (in a potentially vulnerable state) is also not something that people would feel free to do. Because of one law, they are in violation if they don't patch, and because of Microsoft's licensing, they're in violation of the law if they do patch.
So forcing users to make/keep their computers ineligible to be used legally seems to me to be a rather significant loss of functionality.
Gartner has a report of the Worldwide server market for the 3Q 2002 (which grew by 3.1%). Though Apple makes up 1.2% of the server market, their sales of servers increased 273.8% (they were 0.4% 3Q 2001). Seems the XServe is making a positive impression.
How well is the MITRE Corporation regarded in general? How well are the thought of by the government in particular? How influential will their word on things be?
By the way, the document summary shows that it was originally a Microsoft Word Doc titled "Microsoft Word - 3DBD823B-1ABD-0AA6.doc" with the author being www.
Interesting that the DOD uses GnuPG, Linux, Linux (Red Hat), FreeBSD, NetBSD, OpenBSD, OpenOffice, Perl, Perl CGI Scripts, PerLDAP, PHP, Tcl/Tk and TCP Wrappers, amongst others.
Does this decode the latest version of WMA files? What does it do about/with the DRM component of such files? And in consideration of this, will MS use the DCMA (or some "you must have agreed to the EULA not to reverse engineer if you've ever downloaded a WMA file in your life" argument) to shut this effort down?
And while Aqua is not open source, quite a few of the other components are. Like Darwin and all of it's parts. And everything you can get with Fink. And XDarwin (the XFree86 implementation). And all of that stuff. Working correctly, and with eye candy too.
Like this worm, Microsoft hides it's attempts to assert ridiculous rights over your boxes in "plain site" by making them a component of the EULA. It obfuscates it's plan and requires consent before it bends people over and uses them.
It is the brazen sickness that brings reference to Microsoft. Of course, the fact that it employs a signed application to access the Microsoft designed email resource is probably because they are ubiquitous and easy to give up all of their information.
On what do you base this assertion?
on
Blogger Hacked
·
· Score: 1, Troll
You voice the opinion that this is an application-level hack, not related to the fact that blogger runs on IIS/5.0 and Windows 2000. You then proceed to place blame on the heads of application programmers, and draw Apache, PERL and PHP into your frame of reference, asserting them all vulnerable to "this sort of" attack.
What foundation do you have for making these assertions and casting these aspersions? I've yet to see any indication one way or another that forensic analysis has been done on this attack. And considering the extremely well-documented security flaws of both IIS and Windows 2000, and the extreme ease that individuals have had in "owning" such boxes, I'd like to know why you automagically start pointing the finger elsewhere. Because, let's face it: even if it was an application error, Windows/IIS more than likely facilitated the attack and the bloody aftermath.
Are applications and Apache/PERL/PHP vulnerable? Yes. As consistently the source of major security failures? No. Definitely not.
I believe the proper response is ...
on
Blogger Hacked
·
· Score: 2
D'oh!
Worst post ever
Specifically ...
on
Blogger Hacked
·
· Score: 4, Informative
The site blogger.com is running Microsoft-IIS/5.0 on Windows 2000.
Status Blog now has info
on
Blogger Hacked
·
· Score: 5, Informative
As of 10:02 am, the status blog now reports:
Blogger has suffered a security intrusion by a "haX0r." We have all the data that was changed backed up within a
couple hours of the attack, so we can have things pretty much back to normal soon. Of course, we're assessing the
situation as thoroughly as possible to make sure it doesn't happen again. Also, if you store your FTP login information
in Blogger, it wouldn't hurt to change that on your server--though it is unlikely that information was accessed. Sorry
for the inconvenience.
In the middle of his article, RMS stated that there were already US law proposals to "prohibit connecting old computers to the Internet." He states that the CBDTPA is one such law proposal.
While I knew that the CBDTPA contained language that all new products would have to have the proposed restrictions, I don't recall seeing anything about shutting out old, non-CBDTPA, computers. Is this an accurate reading of the proposal, or a stretch meant work us up?
Slashdot Mirror
Considering the licensing requirements of SP3 can put a compliant company on the wrong side of the law (1, 2) I would not consider it to be free (in any sense of the term). But considering the number of problems/issues that SP3 supposedly addresses (in the areas of "application compatibility, operating system reliability, security, and setup"), leaving your system as is (in a potentially vulnerable state) is also not something that people would feel free to do. Because of one law, they are in violation if they don't patch, and because of Microsoft's licensing, they're in violation of the law if they do patch.
So forcing users to make/keep their computers ineligible to be used legally seems to me to be a rather significant loss of functionality.
Fortunately, all of those systems are closed, so I'm sure that security was motto number 1.
Of course, motto number 2 was "Ignore motto number 1".
if he were that concerned about it rotting too soon. Talk about rot from the inside.
In the "Discomforting amount of attention paid on a teenage girl, leave her alone and start meeting some adult women already" sort of a way.
So as it turns out, you are wrong.
Gartner has a report of the Worldwide server market for the 3Q 2002 (which grew by 3.1%). Though Apple makes up 1.2% of the server market, their sales of servers increased 273.8% (they were 0.4% 3Q 2001). Seems the XServe is making a positive impression.
a) Get the latest Jaguar
b) Go to Apple and SuSE and get advice on tuning
c) If it is available under SuSE, use gcc 3.1 for compiling
Moshe admitted that there was probably alot of optimizations that he missed. I'd like to see them both tuned for speed and then compare them.
By the way, the document summary shows that it was originally a Microsoft Word Doc titled "Microsoft Word - 3DBD823B-1ABD-0AA6.doc" with the author being www.
Interesting that the DOD uses GnuPG, Linux, Linux (Red Hat), FreeBSD, NetBSD, OpenBSD, OpenOffice, Perl, Perl CGI Scripts, PerLDAP, PHP, Tcl/Tk and TCP Wrappers, amongst others.
Does this decode the latest version of WMA files? What does it do about/with the DRM component of such files? And in consideration of this, will MS use the DCMA (or some "you must have agreed to the EULA not to reverse engineer if you've ever downloaded a WMA file in your life" argument) to shut this effort down?
Did you read the parent post?
You name it, OS X has it (or can get it with Fink).
Warning: Virtual Desktops.app is not yet compatible with 10.2.
Shareware ($20.00), but you can use it with two windows as nagware.
And while Aqua is not open source, quite a few of the other components are. Like Darwin and all of it's parts. And everything you can get with Fink. And XDarwin (the XFree86 implementation). And all of that stuff. Working correctly, and with eye candy too.
It is the brazen sickness that brings reference to Microsoft. Of course, the fact that it employs a signed application to access the Microsoft designed email resource is probably because they are ubiquitous and easy to give up all of their information.
What foundation do you have for making these assertions and casting these aspersions? I've yet to see any indication one way or another that forensic analysis has been done on this attack. And considering the extremely well-documented security flaws of both IIS and Windows 2000, and the extreme ease that individuals have had in "owning" such boxes, I'd like to know why you automagically start pointing the finger elsewhere. Because, let's face it: even if it was an application error, Windows/IIS more than likely facilitated the attack and the bloody aftermath.
Are applications and Apache/PERL/PHP vulnerable? Yes. As consistently the source of major security failures? No. Definitely not.
Worst post ever
The site blogger.com is running Microsoft-IIS/5.0 on Windows 2000.
Blogger has suffered a security intrusion by a "haX0r." We have all the data that was changed backed up within a couple hours of the attack, so we can have things pretty much back to normal soon. Of course, we're assessing the situation as thoroughly as possible to make sure it doesn't happen again. Also, if you store your FTP login information in Blogger, it wouldn't hurt to change that on your server--though it is unlikely that information was accessed. Sorry for the inconvenience.
For those with more disposable income, as long as they keep the Cherry 2000 model out of the water, everything should be fine.
What does ...God...need with a starship?
I ...Am ...KIROK!!!!
Khan!!!
Khannnnnn!!!
Khannnnnnnnnn!!!
In fact, after a few hours in the sun, that might be the medium of attack itself. Spoiled Mayonnaise: The Ultimate Weapon(tm)
You can look at the info on it in English at http://www.panasonic.com/consumer_electronics/dvd_ recorder/dvd_recorder.asp
While I knew that the CBDTPA contained language that all new products would have to have the proposed restrictions, I don't recall seeing anything about shutting out old, non-CBDTPA, computers. Is this an accurate reading of the proposal, or a stretch meant work us up?