This is just another instance of Microsoft attempting to move the responsibility for the security of its products onto a third party. The bottom line is Microsoft's products are a threat to (fill in your country here) national security. In the past they have been able to fall back on the good graces of the worm writers who have not unleashed truly malicious code or code that transmitted corporate secrets into a public forum such as Usenet. Will it take a WTC class worm to make users of their software buy a clue and start looking for alternatives?
A few years ago an IBM business unit EduQuest manufactured a 386 class computer that came with a ton of family and educational software. A few weeks before they were supposed to start shipping someone added up the space the programs were going to take up (duh) and realized the disk drive wasn't large enough. No problemo! They substituted MS-DOS for PC-DOS and DoubleSpaced the drive, leaving just a few MB left for data. Upon first bootup, users saw a message that instructed them to go buy 70 floppies and back up the system before using it.
If their requests go through a cacheing proxy server then the files that were requested and the ip address of the requesting machines may be in a log file.
1) How would you implement a backup strategy?
2) How can you prove that you can restore all systems to the same state they were in prior to a catastrophic failure of all systems?
3) Why are manhole covers round?
I have an old Leading Edge 8088 box sitting on a shelf that is full of promises and predictions for the future. Some day I'll crank it up and compare the predictions with reality.
"The Internet has become indispensable to our national security and economic well-being," said Ron Dick, head of the National Infrastructure Protection Centre, an arm of the FBI. "Worms like Code Red pose a distinct threat to the Internet."
Duck and cover.
Create a perl proxy to filter the ads and popup code. Randal Schwartz published some examples in WebMethods some time back. There was also a suggested solution for Mozilla in 1998: http://groups.google.com/groups?q=perl+popups+prox y&hl=en&safe=off&rnum=2&selm=19980911103828-camero n-1-21032%40sid.research.canon.com.au
The problem is the widespread use of Microsoft software in general, particularly the MS Office suite. Although this particular virus sends random files to addresses in the address book, a similar virus could be much more devastating to a company by searching for sensitive documents and posting those to Usenet.
>>
"However, there is a very small percentage of people who have lost their contact list due to unforeseen circumstances in the data restoration process."
A warning to sys admins everywhere to make sure the backups you make can restore the system to the state prior to failure.
Slashdot Mirror
This is just another instance of Microsoft attempting to move the responsibility for the security of its products onto a third party. The bottom line is Microsoft's products are a threat to (fill in your country here) national security. In the past they have been able to fall back on the good graces of the worm writers who have not unleashed truly malicious code or code that transmitted corporate secrets into a public forum such as Usenet. Will it take a WTC class worm to make users of their software buy a clue and start looking for alternatives?
But a Beowulf cluster of floppy drives ...
A few years ago an IBM business unit EduQuest manufactured a 386 class computer that came with a ton of family and educational software. A few weeks before they were supposed to start shipping someone added up the space the programs were going to take up (duh) and realized the disk drive wasn't large enough. No problemo! They substituted MS-DOS for PC-DOS and DoubleSpaced the drive, leaving just a few MB left for data. Upon first bootup, users saw a message that instructed them to go buy 70 floppies and back up the system before using it.
They knew what they were talking about when referring to those lazy sysadmins.
.. otherwise I would think they were holding a ton of puts.
If their requests go through a cacheing proxy server then the files that were requested and the ip address of the requesting machines may be in a log file.
1) How would you implement a backup strategy? 2) How can you prove that you can restore all systems to the same state they were in prior to a catastrophic failure of all systems? 3) Why are manhole covers round?
I have an old Leading Edge 8088 box sitting on a shelf that is full of promises and predictions for the future. Some day I'll crank it up and compare the predictions with reality.
They really know how to put the class in class action...
"The Internet has become indispensable to our national security and economic well-being," said Ron Dick, head of the National Infrastructure Protection Centre, an arm of the FBI. "Worms like Code Red pose a distinct threat to the Internet." Duck and cover.
Create a perl proxy to filter the ads and popup code. Randal Schwartz published some examples in WebMethods some time back. There was also a suggested solution for Mozilla in 1998: http://groups.google.com/groups?q=perl+popups+prox y&hl=en&safe=off&rnum=2&selm=19980911103828-camero n-1-21032%40sid.research.canon.com.au
There are pi seconds in a nanocentury.
The problem is the widespread use of Microsoft software in general, particularly the MS Office suite. Although this particular virus sends random files to addresses in the address book, a similar virus could be much more devastating to a company by searching for sensitive documents and posting those to Usenet.
This will have a similar effect to everyone flushing toilets during Super Bowl at half time.
>> "However, there is a very small percentage of people who have lost their contact list due to unforeseen circumstances in the data restoration process." A warning to sys admins everywhere to make sure the backups you make can restore the system to the state prior to failure.
They probably have MS Office running on every employees' workstation.
They tasted just like chicken.
It's time to organize public burnings of Microsoft software! But first, buy puts.