Earlier quoted context omitted.
To protect against bit flips in car fly-by-wire systems, each signal is sent three times with the 2/3 majority making the decision. This happened after the runaway Prius fiasco that may have been caused by a gamma ray. Prior to that incident the fly-by-wire system only sent one signal.
This is really inefficient, two bitflips in the same location will result in a bitflip. For 3x the space surely there's a more resilient scheme that can handle more.
Calling NSA to find your encryption key after a few bits were flipped (2010)
51–60 of 125 posts
Re: Calling NSA to find your encryption key after a few bits were flipped (2010)
#52I wonder what was the design consideration there? If I'd to make a guess, the point of having key in a re-programmable memory (susceptible to such errors) could be that it could be re-programmed later - otherwise it could've been just hardcoded in ROM. Athough if the error was that it was a RAM copy of the key that's got corrupt, this might explain things - no one to reboot the machine around, huh. If re-programmabil…
Re: Calling NSA to find your encryption key after a few bits were flipped (2010)
#53Earlier quoted context omitted.
Bit flips are quite useful for sorting huge arrays of data: https://news.ycombinator.com/item?id=28766154
That's not a proper sort. A sort is not just a function that takes in a list and returns a list that is sorted. The result must also include all of the elements that you had when starting. That property isn't checked by the code you linked.
Re: Calling NSA to find your encryption key after a few bits were flipped (2010)
#54Earlier quoted context omitted.
It's your error, having a system with important data no actual/realtime backup no second system and no plan to recover from a failed update and no ecc is YOUR error alone. However, intel should have made ecc the standard and not just for 1000$+ Xeons.
>However, intel should have made ecc the standard and not just for 1000$+ Xeons. Agree 100%. IMHO, the choice between "domestic" and "industrial-strength" should not mean choosing between different degrees of risks of failure.
Re: Calling NSA to find your encryption key after a few bits were flipped (2010)
#55From the headline I imagined this was something like "We lost our encryption key for some important data, but the NSA had already cracked or stolen it, so they were able to return it to us"
Re: Calling NSA to find your encryption key after a few bits were flipped (2010)
#56Re: Calling NSA to find your encryption key after a few bits were flipped (2010)
#57Earlier quoted context omitted.
>However, intel should have made ecc the standard and not just for 1000$+ Xeons. Agree 100%. IMHO, the choice between "domestic" and "industrial-strength" should not mean choosing between different degrees of risks of failure.
I gather DDR5 will have ECC as standard du to the extreme density of memory that will bitflip a lot more than usual. Yay fo r consumers.
Re: Calling NSA to find your encryption key after a few bits were flipped (2010)
#58Sure I dont know how long the key length was, I dont know how long the encrypted string was, but surely it wouldnt have taken that long to cycle through a number of flipped bits, or would it?
Re: Calling NSA to find your encryption key after a few bits were flipped (2010)
#59Why is traffic from Voyager even encrypted? The results back are public scientific data anyway, right? And it's not like other nations (the only ones with power to transmit that far, back then) would send rogue commands without getting caught.
How would you catch them?
Also, these spacecraft didn't start off outside the solar system. They weren't always so far away that a lone prankster would have trouble sending them messages.
Re: Calling NSA to find your encryption key after a few bits were flipped (2010)
#60I wonder what was the design consideration there? If I'd to make a guess, the point of having key in a re-programmable memory (susceptible to such errors) could be that it could be re-programmed later - otherwise it could've been just hardcoded in ROM. Athough if the error was that it was a RAM copy of the key that's got corrupt, this might explain things - no one to reboot the machine around, huh. If re-programmabil…