Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×

Comment Re:Unpaid labour? (Score 1) 72

Wow, you *are* ignoring the sendmail and bind exploits - many of them were due to lax security rather than being coding bugs.

I'll give you that. I should have called them design or implementation deficiencies, not coding bugs. The Internet began as a really "in-house" sort of thing. They didn't anticipate that their collaborators would go out of their way to abuse what was then a shared and mostly trusted resource. The Morris Worm was pretty much a kid's white hat hacking that (oopsie) got out of control, and SMTP wasn't designed to prevent it. The Green Card Lawyers taught us how robust those systems were - jerks in the system could get anything they wanted to go through and there was little in the way of defence built into the system to stop them. Telnet, ftp, rsh all transmitted passwords en clair. "Oh, was that wrong?" Arpanet was designed to ensure communication wouldn't be disrupted. After all, they weren't expecting the Soviets to have access to any of it.

And you also seem to ignore the thriving antivirus markets that existed for the Atari, Amiga and other non-MS platforms - I wonder how MS was responsible for those!

I never had any of those, so never really cared about them. Then MS showed up so ripe for exploitation, it was a magnet for abuse. How did it work, you could name malicious.exe to malicious.exe.jpg and it would walk right past any defences (which were non-existent)? Meanwhile, MS decided users didn't need to care about file extensions (even while the OS did care), so they were hidden from the user by default. Great.

I can't believe anyone defends MS for the crap they've pulled. You should be livid about their multi-decade abuses, not to mention having had to pay them and other MS ecosystem crap purveyors for the privilege.

Comment Re:Unpaid labour? (Score 0) 72

Is your selective memory ignoring all the sendmail and bind exploits that did the rounds in the 80s and 90s?

No, those were bugs, or things the software wasn't designed to worry about. What produced the malware and spam market? MS' laxity in *everything* system security related, maybe?

Are you ignoring how little MS bothered to secure itself, insisted that's not its problem, could be handled with bolted on (for a price) software supplied by third party suppliers, and it wasn't MS' problem that Win* wasn't able to protect itself?

Latest I heard was *the best* AV software supplied by third party suppliers was *at best* capable of stopping 80% of malware.

Good job. Ass holes!

Comment Re:ex microsoft shill (Score 2, Interesting) 72

The CD problem you refer to is not a fault of the operating system, but rather the drive and the motherboard bios.

Bull. Shit. This goes back to win for workgroups. Copy a file to the floppy drive, takes over the whole damned CPU. They've never known, *had any clue*, as to how to build an OS. They only know how to cash checks from morons (accountants, doctors, lawyers; the stupidest computer users on the planet).

Comment Re:Unpaid labour? (Score 1) 72

I'm sure the Linux distro makers (which often are commercial entities) gladly take your free labor, and laugh at their way to bank.

They're not grabbing my scrotum as they laugh their way to the bank. Oh, you wanted security from malware and viruses and crackers? There are many Microsoft Partners who'd be happy to supply you with solutions ...

Bite me! Microsoft's ineptitude created that pathetic market!

Assholes.

Comment Re:Sounds nice (Score 2) 156

but but but but it does more than one thing, its not the Unix Way ...

That's what you guys have always misunderstood about emacs. It's really an operating system that merely looks like an editor.

Comment Re:Easy to solve - calibrate them to overestimate (Score 1) 398

You're not even supposed to run the amber, never mind the red.

Incorrect. When you see light turning yellow, you are suppose to stop when it is safe to do so, otherwise proceed through the intersection.

If you're seeing Green, what's going to come up next? Yellow. So if you see Green, immediately start to decelerate. If you see Yellow, next to come up is Red, and you may wrongly assume you're going to be given a chance to do anything about it. Oh yeah, that's what seeing Green's all about.

If you see Red, now's your chance to gamble and be an a$$hole because Green's coming up ... sometime.

Comment Re:I am not going to convert (Score 1) 245

If something is working, there's no point in trying to break it.

If something is working, that's the incentive to try to break it. If it survives the attempt, it deserves the respect. If it doesn't (breaks), it gets better (fixed), or replaced. Progress.

I'd like to define this as the Dirty Harry Principle. "Did I fire six shots, or only five?" "Hey man, I gots to know!"

He wants to know *so much* that he's willing to die in order to find out.

Slashdot Top Deals

"If it ain't broke, don't fix it." - Bert Lantz

Working...