@bascule @matthew_d_green I'd use something like HMAC-SHA512("key id for my super-scheme", key) instead of plain SHA-512 to derive keys
-
-
Replying to @dchest2 replies 0 retweets 1 like
-
Replying to @matthew_d_green
@matthew_d_green@dchest@marshray updated using nonces + HKDF: https://gist.github.com/tarcieri/5351974 …2 replies 0 retweets 0 likes -
Replying to @bascule
@bascule@matthew_d_green@dchest@marshray I don’t understand why you’re replacing NaCl with entirely new constructions.1 reply 0 retweets 0 likes -
Replying to @tqbf
@tqbf@matthew_d_green@dchest@marshray just a thought experiment. The stuff I'm actually writing uses secret_box1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@matthew_d_green@dchest@marshray It doesn’t sound that way from the ticket; sounds like you’re saying, “use this for NIST crypto”2 replies 0 retweets 0 likes -
Replying to @tqbf
@tqbf@matthew_d_green@dchest@marshray so I take it you think even exposing it at all is a bad idea2 replies 0 retweets 0 likes -
Replying to @bascule
@bascule@matthew_d_green@dchest@marshray That doesn’t make it a crime for you to do it but it does confuse the project charter a bit.3 replies 0 retweets 0 likes -
Replying to @tqbf
@tqbf@matthew_d_green@dchest@marshray question is are algorithms like unauthenticated AES-CTR or XSalsa20 too dangerous to expose at all1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@tqbf@matthew_d_green@dchest expose them under the 'footgun' namespace1 reply 0 retweets 0 likes
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.