Tweets

  1. Not doing tech stuff for a month, skimming twitter for 10 min every 2 days. Feel free, encouraged even, to @/DM/chat me things I should read

  2. I appreciate you explaining Cryptopocalypse well, and not buying into the media's wording :)

  3. Got a nice letter from asking me to reconsider the pulling of the talk and linking to the press release. Nope, sorry but nope.

  4. as far as sha256, I'd dig in & figure out default. I kind of like SHA384, but it's preference not recommendation

  5. Not familiar enough with XTS to know for sure. Quite possibly, but I'd probably pick it just because

  6. Not standard but easy to implement. However, the sudden-death counter reuse is probably fatal:

  7. A reason to use forward-secure signature schemes for code signing, perhaps?

  8. That _sounds_ sexy, but are any standardized, easy enough to implement, and more likely to be deployed than counter-timestamping?

  9. NSA proving difficulty of code signing revoking: At what date should we invalidate signatures of stolen cert? (Assuming counter-timestamps)

  10. XTS is new default, not vulnerable according to blog. "systems w/ FDE installed w/ 12.04 or earlier are potentially vulnerable"

  11. I hadn't seen news report that DUAL_EC_DRBG as backdoored in '04. I find that part very interesting.

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.