4 ms·
Presumably it's possible to code defensively against this sort of thing, by eg. running the entire operation twice and checking the result is the same before co
by caf 5y ago
Presumably it's possible to code defensively against this sort of thing, by eg. running the entire operation twice and checking the result is the same before committing it to the published log?
- makomk 5y agoBig tech companies like Google and Facebook have encountered problems where running the same crypto operation twice on the same processor deterministically or semi-deterministically gives the same incorrect result... so the check needs to be on done on separate hardware as well.
- caf 5y agoI don't think that matters in this case, because the entire point of the log machine is to run crypto operations. If it has such a faulty processor it is basically unusable for the task anyway.