[tahoe-lafs-trac-stream] [tahoe-lafs] #2018: padding to hide the size of plaintexts

[tahoe-lafs]

#2018: padding to hide the size of plaintexts
-------------------------+-------------------------------------------------
     Reporter:  zooko    |      Owner:  nejucomo
         Type:           |     Status:  new
  enhancement            |  Milestone:  undecided
     Priority:  normal   |    Version:  1.10.0
    Component:  code-    |   Keywords:  confidentiality privacy compression
  encoding               |  newcaps research
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by zooko):

 Hi, Nikita and NickM. I'm really perplexed about this whole topic, because
 I don't know what formal model applies to the real-world cases that I care
 about.

 Just to throw out an example of a model, there's a set '''S''' of files,
 each with a size, and a player '''A''' picks some one file from '''S'''
 and reveals some function of that file's size and/or compression, and then
 the other player '''M''' tries to guess which file '''A''' picked. Is that
 something anyone cares about? I really don't know.

 Something that I'm sure that I do care about is the CRIME/BEAST-style
 attacks on compression. I would feel better about LAFS's resistance to
 those if we added padding (of the kind described in the Description of
 this ticket).

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2018#comment:17>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage