Single random bit flip causes error in certificate transparency log
Isn't ECC memory supposed to mitigate these kind of bit-flips, specifically it should correct all single bit flips?<p>As this is a single bit-flip, why wasn't it corrected? Did ECC memory fail? Or was this bit-flip induced in the CPU pipeline, registers, or cache?<p>Do we need "RAID for ECC memory", where we halve user-accessible RAM and store each memory segment twice and check for parity?