I don't know who needs to know this, but a cryptographic seed can safely generate about 700M times its size in secure random output. Meanwhile a Sequoia seed can generate a Redwood tree that is about 2.5B times its volume.
-
-
Replying to @colmmacc @CiPHPerCoder
It's not really a linear relationship for cryptographic seed sizes. The security often rely on the "birthday bound" which depends on cipher block size. The outdated cipher 3DES-CBC w/ 64 bit blocks (although the key is longer) is safe for ~785 GB data, that's 40B times expansion.
1 reply 0 retweets 1 like -
Replying to @Natanael_L @CiPHPerCoder
That doesn't sound right. I'm not sure what the usage limits would be now in light of sweet32, but it'd have to be much much lower.
3 replies 0 retweets 0 likes -
Take 512-bit seed S. Compute h(S||1) h(S||2) h(S||3)... and produce essentially any length of pseudo random string for a decent hash function hash function h().
1 reply 0 retweets 0 likes
That sounds a bit like HMAC_DRBG or HASH_DRBG; HMAC is considered better for some prediction resistance reasons. Either way, 3DES is a cipher, not a hash :)
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.