Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. ×

Comment Not bloody likely (Score 3, Informative) 89

As FOLDOC explains, Intel tested this idea decades ago by putting one board in a 25 ton lead safe and another outside to see if there was a measurable difference in bit rot. There wasn't. " Further investigation demonstrated conclusively that the bit drops were due to alpha particle emissions from thorium (and to a much lesser degree uranium) in the encapsulation material." They ended up redesigning the memory to be more resistant to the effect.

Comment Re: Wot? (Score 1) 75

ther material is cheap. THe labor is expensive. 20/hr or more for doing that work. In the same length of time that it takes to put the plywood down on the rafters, is about the same length of time for putting down the Tesla Roof. So, no tar paper or shingles, which is money and time. And we just had our roof re-done 3 weeks ago. I forget how many sections, but, iwe have a 2 story 3000 sq feet home, so above average roof. We had 8 guys work on it. Took 1.5 days. That is the second time that we have had this done due to hail. Next time, we will install a Tesla roof which will almost certainly be strong enough to deal with the golf ball size hail that we get.

Comment Re:Yahoo has users? (Score 1) 169

Even in those early days of AltaVista and Lycos I can't ever recall using Yahoo.

I can't ever recall using AltaVista and Lycos. Of course, I came late to the Internet GUI scene. My first five years on the Internet was on a dial-up SLIP account into a UNIX box and using Lynx (text web browser) to browse the Internet.

Comment Re: Better gadget (Score 1) 210

The assumptions I'm making are the most-generous most in-your-favor assumptions I can reasonable make.

Your assumptions are shit.

I'm pretty sure you'd be an asshole no matter where you worked.

Someone has to get the job done.

And from the pissing and moaning you've done here in the past about your help desk gigs and difficulty finding jobs after being outsourced, I'm pretty sure the "highly paid" thing is just about as real as your "75 pounds of muscle gained in just a year."

I've never been outsourced from any job in the last 20+ years of my IT career. I'm a contractor. I do contract work. The contract can last one day to one year. I'm currently two years into a five-year contract for government IT that's fully paid for by your tax dollars. That also includes paid federal holidays, 20 Paid Time Off (PTO) days, healthcare/dental/vision and 401k. If the Republicans shut down the government tomorrow, I'll still be working since I'm an essential employee.

Comment Re:Totally. (Score 4, Interesting) 121

Well considering that only Americans could be dumb enough to think this kind of low level data is "such sensitive information"

Apparently, you don't understand anything about the physical security of dignitaries and top officials.

Travel plans, routes, and details about the stops of heads of state are always considered highly sensitive security information. This country is full of extremely stupid, gullible, and ridiculously-overarmed people, and a small subset of whom probably thinks it would be a good thing to bring harm to the First Lady. The Secret Service plans the routes, the stops, provides decoy vehicles, and secures each of those locations to an incredible degree; but no amount of effort can secure every location against a patient, well-camouflaged, entrenched sniper. Uncertainty in the travel routes is one of the best ways to keep the lone wolves from being able to plant themselves along the route.

So yes, it is highly sensitive information.

Comment Re:They've already tacitly admitted the breach (Score 1) 169

I remember I also had to change passwords on Yahoo! about two years ago.

I believe there's a clue in their "Breach FAQ" where they state "the vast majority of passwords were hashed with bcrypt". It could be that their old passwords were protected with a less-secure older salting-and-hashing system, (maybe something like the original crypt() ) and by 2014 they had replaced it with bcrypt.

But even an old crypt() hash can't simply be broken on demand without a lot of CPU grinding for every password recovered. Because the old passwords were hashed, there would have been no easy way for Yahoo! to automatically migrate them into bcrypt. So after the system conversion was complete, they prompted all users to change their old passwords so they would migrate themselves to the new bcrypt-based system. People who haven't logged in since 2014 probably still have the old original hashed passwords on file somewhere at Yahoo HQ..

Slashdot Top Deals

All life evolves by the differential survival of replicating entities. -- Dawkins

Working...