[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2165: use bigger random one-time keys, rename to "timing_safe_compare"

[Tahoe-LAFS]

#2165: use bigger random one-time keys, rename to "timing_safe_compare"
-----------------------------+-------------------------------------
     Reporter:  zooko        |      Owner:  daira
         Type:  enhancement  |     Status:  closed
     Priority:  normal       |  Milestone:  1.11.0
    Component:  code         |    Version:  1.10.0
   Resolution:  fixed        |   Keywords:  cleanup security timing
Launchpad Bug:               |
-----------------------------+-------------------------------------

Comment (by warner):

 That *is* funny. Yeah, I remember thinking that I didn't have time to
 analyze it properly, and being freaked out that it's easy to get the first
 few bytes of the target, so a randomized hash would be the most
 conservative approach.

 I like your hash-it-once-and-store-it approach. For our purposes, I guess
 that'd mean storing H(write-enabler) instead of write-enabler, so the
 potentially-leaky hash occurs at mutable-share creation time, not
 subsequent access time.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2165#comment:13>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage