(1) you gotta do your homework, folks. If you just believe that the patch was installed and don't actually check, then you're a fool.
(2) home users, like it or not, ARE the sysadmin. They must take responsibility for their action or inaction. Failure to patch a system because they didn't know how ("better damn well learn!") or "I'm too busy" or "It's too hard!" is not an excuse. If you can't be reliable enough to patch and to own up to the responsibility then you shouldn't have a computer, let alone one connected to the Internet. All these arguments are just as silly as not wearing a condom when fucking the neighboorhood whore, try that, and see what you bring home for the ride.
(3) It doesn't matter one iota if gnuftp was "inside" or not. It matters that all the data and source was compromised. That's a bigger deal than MSBlaster. The only thing that could trump it would be if MS' inside source repository was similarly compromised. If you can't keep inside security tight, then how can you be trusted to keep outside security tight? You can't.
MSBlaster wasn't an embarrasment for MS, but for the lazy sysadmins who, with a month's prior notice and the patch to fix it, were still hobbled by the bug. If people who are in charge of systems and security spent more time patching and paying ATTENTION to things like Bugtraq and less time complaining about MS the world would be safer.
How is this bug more of a bummer than how gnuftp was compromised and potentially more damaging? Oh, don't hear people moaning about that on here now do you...?
"Palm" was easy, simple, and only 4 freaking letters! Plus their ticker was PALM! Hello?! Going to PalmOne is longer, dumber, and not as intuitive, plus their ticker changed...
Then who is left for the remaining 50% of the crashes?
From MS' point of view:
"First Party" software = written by Microsoft
"Second Party" software = written by the end user
"Third Party" software = written by someone other than the end user or MS.
Clearly some software is written by end users, my company is an "end user" and we write mission-specific apps all the time. So, if our apps are only responsible 1% of the time for the crash that means that MS is only responsible 49% of the time. Which makes Third Party more guilty than others. And that's only assuming our apps are at that 1% failure rate, I would bet it's higher than that without even looking up the stats (probably more like 10 to 15%, I'd wager). As a result, MS is not responsible for 50% of the crashes.
I know I'll get modded WAY the fuck down, but I don't care...
This whole thing is flamebait. The article title "Microsoft Code at Fault for Half of all Windows Crashes" should have been "Thrid Party Code at Fault for Half of all Windows Crashes"...or is it that only anti-MS articles get posted? So much for having any integrity, Slashdot.
but to be slow at patching servers and systems is just plain stupid. Any system not patched up when you had a month to get the patch deserves to be hit hard. Lazy sysadmins need their asses handed to them, it will weed out the weak and we intelligent people will get the better pay. It's good for all of us in the long run.
Nowhere does it say "commerical" in the article. Not once. It does say "U.S. Software," which would also include non-commercial types (like for instance your favorite disto of Linux, provided you can get tech support for it--because you paid for it.)
1. Samba has got to be one of the most useful pieces of software I use.. and to suggest that half of it doesn't work really suggests that you don't know what you are doing.
If you follow the directions in the SAMBA manual and documentation exactly, even duplicating their user structure (to make sure you get it right) users still will not authenticate properly. That's the problem. You can use the web interface or you can wade through the files manually, doesn't matter, it is still borked. Half the time the user with authenticate fine, other thies the server will issue errors the the effect of "huh?"
SAMBA is broken. I am surprised anyone has any sort of success with it.
SAMBA is crap and should be redone from scratch, half the damn time the shit just doesn't work.
For Novell, it would be nice if you didn't have to putz around with ncpfs and that to get on a Netware server. Novell (hopefully) will fix this soon (now that they own Ximian) and will make a real client for Linux. That would solve that.
X sucks. It should be redone from scratch too. There's so much functionality that they could do but are hanging on to old leftover crap...just junk it and make a new X.
Oh, and the "RTFM," and "read the MAN page..." assholes. Gee, ya think people don't START there or something? WTF? I can't count the number of times I ask a question, telling people I've read the fucking manual already and read the MAN pages and still can't get something to work only to have some felch-monkey tell me "RTFM". It's even cooler when they quote my WHOLE FUCKING POST only to add "RTFM" at the bottom. Your leetness makes me jizz, you fucking cock-snot!
ARGGGGGH! Too many Linux people have head-up-ass-syndrome. For a community of enthusiasts there sure are a lot of dipshits.
There was considerable debate with the ranks of the Apostles themselves over all those things and they only came to the conclusions they did because they needed "fresh blood" or their little cult would have died. It seems that necessity is also the mother of religion as well as invention.
ro read that section fo Duteronomy, it's right there in front of you. That's "God's words" not mine. Plus I cut-n-pasted from the skeptic's site, so don't be pulling your AC shit with me, fartknocker.
My favorite is Deuteronomy 23:2...God won't let bastards attend church. Neither can the sons or daughters of bastards "even to the tenth generation." So if you plan to attend church next Sunday be ready to prove that your genitals are intact and don't forget your birth certificate and genealogical records for at least the last ten generations. Don't laugh. This stuff is important to God.
There's rape, murder, infanticide, mass killing, cult activity, genocide, supernatural beings, and talking animals. Surely these things should not be allowed!
Other's will, but I won't simply because (for me) the Internet itself is the content that I'm after, if I wanted hallow content I'd use AOL or something.
but this guy is a dope, he EASILY could have just bought a computer (barebones) with no OS installed and saved himself a shitload of problems, but that asside, what he really wanted to do was "stick it to the man" and get $199 back on his PC purchase. That's nice and all, but how much time did he spend on the case, documentation, calls, etc? Work it out and that $199 is pittance. Even with court costs he is out money for trying to be cool.
In short: he should have just stuck with the copy of XP and used it as a really expensive coaster or buy a barebones system and save the difference, time, and hassle.
That's clearly incorrect, the gov't can take your pc and do whatever they want with it, read about how Steve Jackson Games was raided by the Secret Service and had their equipment taken and many files compromised. Sure the SS lost that case, but do you think that ws an isolated incident? I don't.
MS will just wave a few bills in their face and say "shut up, go away." And they will. Either that or MS will take some of their $40B and just buy the whole company from them. Then the IP is theirs. This isn't that had of a thing to do for them...I mean, they're rich!
For us Slack users, although this is a bit old, it's still pretty valuable, check this out. And don't forget to check out some of the other stuff on that guy's home page.
Slashdot Mirror
(1) you gotta do your homework, folks. If you just believe that the patch was installed and don't actually check, then you're a fool.
(2) home users, like it or not, ARE the sysadmin. They must take responsibility for their action or inaction. Failure to patch a system because they didn't know how ("better damn well learn!") or "I'm too busy" or "It's too hard!" is not an excuse. If you can't be reliable enough to patch and to own up to the responsibility then you shouldn't have a computer, let alone one connected to the Internet. All these arguments are just as silly as not wearing a condom when fucking the neighboorhood whore, try that, and see what you bring home for the ride.
(3) It doesn't matter one iota if gnuftp was "inside" or not. It matters that all the data and source was compromised. That's a bigger deal than MSBlaster. The only thing that could trump it would be if MS' inside source repository was similarly compromised. If you can't keep inside security tight, then how can you be trusted to keep outside security tight? You can't.
MSBlaster wasn't an embarrasment for MS, but for the lazy sysadmins who, with a month's prior notice and the patch to fix it, were still hobbled by the bug. If people who are in charge of systems and security spent more time patching and paying ATTENTION to things like Bugtraq and less time complaining about MS the world would be safer.
How is this bug more of a bummer than how gnuftp was compromised and potentially more damaging? Oh, don't hear people moaning about that on here now do you...?
The tale is telling, is it not?
Bah. I thought it said "Internet Nookie" ...
"Palm" was easy, simple, and only 4 freaking letters! Plus their ticker was PALM! Hello?! Going to PalmOne is longer, dumber, and not as intuitive, plus their ticker changed...
Bad idea.
Then who is left for the remaining 50% of the crashes?
From MS' point of view:
"First Party" software = written by Microsoft
"Second Party" software = written by the end user
"Third Party" software = written by someone other than the end user or MS.
Clearly some software is written by end users, my company is an "end user" and we write mission-specific apps all the time. So, if our apps are only responsible 1% of the time for the crash that means that MS is only responsible 49% of the time. Which makes Third Party more guilty than others. And that's only assuming our apps are at that 1% failure rate, I would bet it's higher than that without even looking up the stats (probably more like 10 to 15%, I'd wager). As a result, MS is not responsible for 50% of the crashes.
I know I'll get modded WAY the fuck down, but I don't care...
This whole thing is flamebait. The article title "Microsoft Code at Fault for Half of all Windows Crashes" should have been "Thrid Party Code at Fault for Half of all Windows Crashes"...or is it that only anti-MS articles get posted? So much for having any integrity, Slashdot.
but to be slow at patching servers and systems is just plain stupid. Any system not patched up when you had a month to get the patch deserves to be hit hard. Lazy sysadmins need their asses handed to them, it will weed out the weak and we intelligent people will get the better pay. It's good for all of us in the long run.
Nowhere does it say "commerical" in the article. Not once. It does say "U.S. Software," which would also include non-commercial types (like for instance your favorite disto of Linux, provided you can get tech support for it--because you paid for it.)
Remember, the "help" button ususally doesn't.
1. Samba has got to be one of the most useful pieces of software I use.. and to suggest that half of it doesn't work really suggests that you don't know what you are doing.
If you follow the directions in the SAMBA manual and documentation exactly, even duplicating their user structure (to make sure you get it right) users still will not authenticate properly. That's the problem. You can use the web interface or you can wade through the files manually, doesn't matter, it is still borked. Half the time the user with authenticate fine, other thies the server will issue errors the the effect of "huh?"
SAMBA is broken. I am surprised anyone has any sort of success with it.
Ohh, will you fix that whole no multiple wife thing too? That would rock! Do that and you're my Apostle! :)
SAMBA is crap and should be redone from scratch, half the damn time the shit just doesn't work.
For Novell, it would be nice if you didn't have to putz around with ncpfs and that to get on a Netware server. Novell (hopefully) will fix this soon (now that they own Ximian) and will make a real client for Linux. That would solve that.
X sucks. It should be redone from scratch too. There's so much functionality that they could do but are hanging on to old leftover crap...just junk it and make a new X.
Oh, and the "RTFM," and "read the MAN page..." assholes. Gee, ya think people don't START there or something? WTF? I can't count the number of times I ask a question, telling people I've read the fucking manual already and read the MAN pages and still can't get something to work only to have some felch-monkey tell me "RTFM". It's even cooler when they quote my WHOLE FUCKING POST only to add "RTFM" at the bottom. Your leetness makes me jizz, you fucking cock-snot!
ARGGGGGH! Too many Linux people have head-up-ass-syndrome. For a community of enthusiasts there sure are a lot of dipshits.
There was considerable debate with the ranks of the Apostles themselves over all those things and they only came to the conclusions they did because they needed "fresh blood" or their little cult would have died. It seems that necessity is also the mother of religion as well as invention.
ro read that section fo Duteronomy, it's right there in front of you. That's "God's words" not mine. Plus I cut-n-pasted from the skeptic's site, so don't be pulling your AC shit with me, fartknocker.
My favorite is Deuteronomy 23:2...God won't let bastards attend church. Neither can the sons or daughters of bastards "even to the tenth generation." So if you plan to attend church next Sunday be ready to prove that your genitals are intact and don't forget your birth certificate and genealogical records for at least the last ten generations. Don't laugh. This stuff is important to God.
There's rape, murder, infanticide, mass killing, cult activity, genocide, supernatural beings, and talking animals. Surely these things should not be allowed!
Other's will, but I won't simply because (for me) the Internet itself is the content that I'm after, if I wanted hallow content I'd use AOL or something.
but this guy is a dope, he EASILY could have just bought a computer (barebones) with no OS installed and saved himself a shitload of problems, but that asside, what he really wanted to do was "stick it to the man" and get $199 back on his PC purchase. That's nice and all, but how much time did he spend on the case, documentation, calls, etc? Work it out and that $199 is pittance. Even with court costs he is out money for trying to be cool.
In short: he should have just stuck with the copy of XP and used it as a really expensive coaster or buy a barebones system and save the difference, time, and hassle.
That's clearly incorrect, the gov't can take your pc and do whatever they want with it, read about how Steve Jackson Games was raided by the Secret Service and had their equipment taken and many files compromised. Sure the SS lost that case, but do you think that ws an isolated incident? I don't.
where the role of violence becomes legitimate in the quest to become a cyborg.
Violence aginst others (forcing cybernetic implantation--i.e.: assimilation) or violence against one's self (stupidity)?
MS will just wave a few bills in their face and say "shut up, go away." And they will. Either that or MS will take some of their $40B and just buy the whole company from them. Then the IP is theirs. This isn't that had of a thing to do for them...I mean, they're rich!
Nobody mentioned the great value of nmap yet? Geez, yer all getting sloppy.
MS did this in Windows 2003 Server. Everything is off by default and you have to turn it on to get stuff to work.
For us Slack users, although this is a bit old, it's still pretty valuable, check this out. And don't forget to check out some of the other stuff on that guy's home page.
This is the end...
...I'm not sure Bush can read at all anyway.