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

 



Forgot your password?
typodupeerror
×

Comment Re:Read the Followups (Score 1) 321

Someone mod this insightful? Come on it's "obvious" that everyone in the UK Border Agency were all sat around reading Slashdot this morning, http://yro.slashdot.org/story/13/08/18/1641241/wikileaks-releases-a-massive-insurance-file-that-no-one-can-open and then spotted this guy's name popup on some list, put two and two together and ended up with a prime. ;^)

Comment Best available advice? (Score 1) 148

I imagine this has crossed (or should have) the minds of a few people here, is there any "credible" advice about the theoretical process and the best/least-worst practical actions to take if you're approached by your friendly local domestic intelligence agency and told to pony up your company's private keys (for example) along with the explicit instructions not to inform anyone else, ever? For the record I'd like to declare that I've never been in that or any similar position.

Comment Re:Where's the story? (Score 1) 318

He's not reporting a bug, he's reporting a security vulnerability which may indeed be a subset of "bug" but it's a very special subset of bug, the sort where even senior management are obliged to get their finger out of their arse and "Do the Right Thing". Especially given eBay are an American company as I seem to remember yanks being big on this thing called "Fiduciary duty to shareholders" which will most certainly not be served, even in the short-term, let alone the medium or long-term by sticking two fingers up at this kid.

Comment Re:... are probably none (Score 1) 148

...they may have made some implementation faults that will allow an attacker to falsely keep their checks happy while still modifying boot files.

Well that to.

The key is probably only useful for signing firmware, probably only for this vendor and possibly only for this chipset, maybe even a single main board.

TFA implies it was for "Ivy bridge" so yeah probably tied to chipset, maybe multiple boards but the point is they've demonstrated something arguably close to gross incompetence, misplacing source code is careless, misplacing the signing key is a different league. This is a commercial product how hard would it be to have the key in two parts, held by two individuals on the dev/release team?

This system is built purely on trust and its gone, I mean, yeah "I'm sure they'll be more careful next time" but sarcasm aside there's no real way for them to demonstrate that.

The truly paranoid might even point out that if someone with the means found the FTP server first they could already have trojaned AMI's build servers (running AMI bioses no doubt) with a root kit tainted bios that produced new tainted bioses during compilation and lo' all AMI bios forever after are hence tainted in a never ending FUBAR circle of doom!!!

With three entire exclamation marks and all assuming it's genuine.

Slashdot Top Deals

He has not acquired a fortune; the fortune has acquired him. -- Bion

Working...