Shouldn't we be welcoming RdRand with open arms? It's a mathematically proven high-quality random number generator that lets chips like Ivy Bridge & Haswell produce large amounts of true random data (not a simple PRNG data) at multi-gigabit speeds.

I'm guessing they are implying that the stream coming from RdRand isn't actually random, but perhaps an AES encrypted stream that the NSA has the key for. Not that I've ever seen any proof of that, it seems maybe in the tin foil hat realm..but who knows what hides in intel's microcode?

Then if you don't understand how to make this sort of change, then you aren't smart enough to understand why you should or should not be using RDRAND it in the first place.

You have the source code, remove rdrand from the kernel yourself.

It sure sounds like Microsoft wants to be like Big Blue, making their big bucks in consulting services. It seems to be working out okay for them, I'm not entirely sure Microsoft however can manage not to shoot themselves in the foot in trying it.

It also seems that there is two classes of EPIRBS, the class I activates automatically and the class II which is a manual activated device. If it was a class II device and they went down in a hurry there might not have been time to activate it either. I have no clue which type of device they had onboard.

If anything, it is certainly is a reminder that the ocean is still a very dangerous place.

I just googled a bit for further information about the ship and came across a rather interesting thread: http://www.cruisersforum.com/forums/f121/schooner-nina-merged-3-threads-105498.html

It appears the ship is equipped with an EPIRB that hasn't been activated apparently. Perhaps they really are just offcourse and not lost.

This sounds like what these guys were doing: http://hardware.slashdot.org/story/12/06/25/1215246/twisted-oam-beams-carry-25-terabits-per-second

Not sure if its the same groups or not, but pretty much the same idea.

Why wouldn't you just be able to play a video back to it of the subject making the required facial expression?

We do the same with alcohol as well, it's called "denatured" alcohol aka poisoned with methyl alcohol or something equally as toxic. We do it for even a more sinister purpose than abuse control, tax revenue.

I second this..debootstrap is your friend. We don't need no stinking installers! :D

See here's the thing, I don't have problems with ads, per-se, I have problem with ads being served by third parties that also serve ads on thousands of other sites as well and track me from site to site. Serve up your ads from your own servers, under your own domain, then I'll see your ads just fine. But if you expect to show me ads that track me, you can go get bent.

it would be a new age of food healthfulness, it would also be a new age of food blandness.

ranch flavored algea soup or garlic flavored algea soup for lunch today?

FWIW I hope i am long dead and buried before food has to suck that bad.

Soylent Green is people!

So it was you who left that on my doorstep this morning!!! :D

1 hour? Give me a fucking break. Doing it in public is as good as launching the attack yourself.

EFnet was fixed within an hour or two for the most part. More importantly the hub servers were not impacted which helped with getting things working sooner.

The patch could have been discussed behind closed doors. If you wanted to get someones attention about the real threat, you could have popped a single server ONCE without making it public.

Indeed the patch could have been discussed behind closed doors, but sometimes zero day things happen. The real question is how do you deal with it when it happens.

Do you have any idea what its like running a network like EFNet and coordinating upgrades across all servers? Do you think there are admins awake and ready to be your bitch and patch their servers on your command in all time zones? Currently showing 44 servers linked ... Yea, an hour was plenty of time to deal with the issue ...
You're a douche for even saying what you're saying.

I personally fixed 4 or 5 efnet servers directly and got patches out to the efnet admin community pretty quickly. Neonlod also had patches out pretty quickly as well, sooner than I did actually.

TBH I'm surprised that it didn't happen sooner seeing that the bug had been there since 2004. The bug itself was a combination of errors. First was a code change that was supposed to do parameter count checking for the called function, however zero was put in for the parameter count that was required.

This didn't matter for a while though as the rest of the code didn't rely on that parameter count checking code. However when some additional code was added, it wasn't protected by the old code that didn't care about parameter count, but it expected that the new parameter count code was working(which it wasn't) thus a command with an empty parameter caused the core dump. Fail.