Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×

Comment Re:Finally big enough? (Score 1) 275

Noah had it easy back then. No one knew about bacteria, and no one ever dreamed in their wildest dreams that there were such things as viruses (whose status as life forms is debatable anyway). That's why all you ever see in the illustrations is giraffes, elephants, cattle and so on. As far as I can tell, it never occurred to anyone to wonder how insects were dealt with.

The ark was only 159 meters long if you take the Egyptian royal cubit as 529 mm. I'm pretty sure the animals had special orders not to eat or shit for the duration, because then it would have required a LOT more than two of each, eh? Also, losses must have been waved away - same reason.

Comment Wikipedia article deleted (Score 1, Flamebait) 98

If Wikipedia was a person I would smack it upside the head for shit like this. There is absolutely no reason not to have an article on LMDB, and deleting a perfectly good article for no reason is evidence of a mental disorder. It's not like they have to spend an extra penny for a piece of paper to hold the article, possibly making the book too thick. Wake up.

Yeah, I'm FAR from a Wikipedia hater, but when it pulls shit like this it reveals its stupidity.

Comment Re:It only takes one ... (Score 1) 381

You know, there is this thing called short term disability. Here's how the conversation goes with your employer. "Hi, I might have been exposed to a moderately communicable, and highly deadly virus. I'm going to need to be put on short term disability for the next 3 weeks while I'm monitored. BTW, firing somebody for being put on short term disability is highly illegal and I'll sue your ass off if you do."

All problems solved, they maintain 90% of their pay, don't put others at risk, and the employer loses nothing because it's an insurance policy that if they're of any size are required to carry anyway.

What fairy tale world are you living in?

Comment Re:Does anyone still use Gnome? (Score 1) 60

Nail, meet hammer's head. Great post. You destroyed all the stupid carping very concisely.

But I have an objection that is genuine, and it is a showstopper.

There is only one thing that prevents me from using KDE. I have tried, oh how I have tried, and I love everything about KDE except this this one thing. Tthe icons in the goddam taskbar won't stay put! You can't keep track of the ordering to find them because the layout keeps changing! Annoying as hell and more, because I absolutely can't use it like that. And they refuse to fix it! All they have to do is make it work dead simply, like Gnome 2 always worked; like Mate works. But they have this fucking oh-so-intelligent sorting algorithm that keeps flipping around the layout. Ugh, just ugh.

Undone by the simple refusal to fix one critical misfeature.

Comment Re:security methods can be used by both sides (Score 2) 37

P.S. - for anyone who is bewildered, when I said "now this" I was referring to the SSL 3.0 exploit. The story is close to this one and I was reading both of them. But it all comes together into a giant shitstorm, and it is past the point of criticality.

Either we are going to abandon the whole internet/OS infrastructure hodgepodge that has proved to be unprotectable and replace it with something that is secure by design, or we are going to have to live with everybody getting constantly pwned. I doubt I will live long enough to see the former, even if it is attempted.

Comment Re:security methods can be used by both sides (Score 1, Troll) 37

That was my question too... how did it get there? I mean, kernel modules don't just magically appear and install themselves... :-P

Using any of the endless parade of exploits that constantly emerge for linux, I would imagine. Why does it matter?
1) You get root just one time
2) Then you can install any kind of root kit or do any other kind of goddam random or fiendishly convoluted havoc you can think of

You know the kind of shabby security joke that Windows turned into? The same thing has happened to linux and BSD - and I say that as a HUGE booster of open source. It's been building relentlessly, but it became official this year with HeartBleed, ShellShock, and now this. And note that this latest is fundamentally different from any of the usual exploits. This one is NOT a bug in any IMPLEMENTATION of the protocol SSL 3.0. It is the discovery that the DESIGN of the protocol has been broken all along. You can't "fix" it by finding some coding boo-boo. It is vulnerable when working AS DESIGNED. If you update the protocol, then it's not SSL 3.0 any more and all kinds of people get cut off from secure access to various servers until everybody is moved over to TLS.

You have two choices:
1) Remove SSL 3.0 protocol capability from ALL clients everywhere, or all servers everywhere, or go after both of them tearing it out. This will break the internet until all servers and clients support AND USE TLS.
2) Live with passwords and other secure data getting pwned right and left.

If you think I've misinterpreted the problem, please tell me exactly where.

Comment Re:To their defense (Score 1) 314

[This is in FUN but it's strictly true] Listen sonny, when I was a kid you went to a GAS STATION to get gas (my father favored the Jenny station). The guy there wore a uniform and he ran out when your car drove over the pneumatic bell-ringer (ding-ding!). Regular people were not allowed to pump gas, and why would they want to when they did it free at the gas station> "I'll have five". "Will that be 5 gallons or 5 dollars?" "Check the oil, sir?" "Do the windshield?" "Could I have a map of the state please?"

Slashdot Top Deals

If you have a procedure with 10 parameters, you probably missed some.

Working...