Replace the RNG based IV with deterministic construction about conceal HOT 3 OPEN

Just curious, why not use SecureRandom output / OpenSSL RNG to generate 16 bytes of "random" data and use that as the IV?

from conceal.

We current do use SecureRandom to generate both IVs and keys with a fix for the SecureRandom android bug. AES-GCM is special in that repetition of the IVs can have serious implications for it's security.

NIST recommends that constructions using a random number limits the use of a key to 2^32 invocations: see http://csrc.nist.gov/publications/nistpubs/800-38D/SP-800-38D.pdf. However with a deterministic construction we can have a higher limit without violating the uniqueness requirement.

There is another task open to use OpenSSL as the RNG for keys.

from conceal.

Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.

from conceal.