why Tink uses a random nonce, not a counter:https://groups.google.com/forum/#!topic/tink-users/v4ATADoH0hU …
Your argument re: 1/2^32 chance of collision is common, but I don't think enough people find it convincing. TLS WG rejected it, for example.
-
-
Also, why bother with 96-bit random nonces if 192-bit random nonces are still on the table? Seems counter to overall goals to offer both.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.