4 ms·
On the other hand, the author of the Bitcoin Wallet Android app thinks it's a SecureRandom problem: https://code.google.com/p/bitcoin-wallet/source/detail?name=
by VMG 13y ago
On the other hand, the author of the Bitcoin Wallet Android app thinks it's a SecureRandom problem: https://code.google.com/p/bitcoin-wallet/source/detail?name=bitcoinj-0.10&r=04d2044880d88107ee4a939a516fb4be4cedeaf9# https://code.google.com/p/bitcoin-wallet/source/detail?name=...
- Buge 13y agoYeah but the current problem with SecureRandom is that it returns the same random number more than once. That armoredbarista page only describes cases where the numbers are less random than they should be, not that they are returned multiple times.
- lwf 13y agoThat commit series doesn't actually appear to use the new class, besides initialising it. Simply initialising it is insufficient, because you need to call addProvider() (cf. https://developer.android.com/reference/java/security/Security.html https://developer.android.com/reference/java/security/Securi... ) to actually have any effect.
- gojomo 13y agoThe LinuxSecureRandom class has a 'static initializer' block, which will run as soon as the class is loaded. (That is, triggered by the reference and initialization call, but just before.) It purports to install LinuxSecureRandom as a new systemwide default (LinuxSecureRandom, lines 56-57).