Re:Bitcointalk Server Compromised
by Dylan16807 on Sunday May 24, 2015 @05:47PM
(#9597754)
If I think the risk is high enough to worry about, I'm going to use a method that gets close to eliminating it. I'm not going to settle for only removing one vector.
[ Parent
| on HN ]
Re:Bitcointalk Server Compromised
by imaginenore on Monday May 25, 2015 @06:00AM
(#9599334)
So don't. Using an airgapped computer will not save you against against a compromised RNG (e.g. reduced entropy). Your computer-generated numbers might look random to you, but you can't really be sure.
Re:Bitcointalk Server Compromised
by Dylan16807 on Monday May 25, 2015 @09:10AM
(#9599893)
>So don't.
Isn't that my argument? Maybe I should try again to clarify my position.
'Just' an airgapped computer solves neither backdoored RNG nor backdoored bitcoin software.
A trusted airgapped computer comes close to solving both.
Using dice only gives me half a solution; why bother?
Re:Bitcointalk Server Compromised
by imaginenore on Tuesday May 26, 2015 @05:59AM
(#9603742)
Airgapped computer definitely solves the compromised software/firmware problem, because it can't send your private keys to the attacker.
Re:Bitcointalk Server Compromised
by Dylan16807 on Wednesday May 27, 2015 @02:04PM
(#9613195)
Compromised software can do anything a compromised RNG can do and more. Especially with something finicky like asymmetric crypto.