[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:
         Type:           |     Status:  new
  enhancement            |  Milestone:  undecided
     Priority:  normal   |    Version:  1.10.0
    Component:  code-    |   Keywords:  confidentiality privacy compression
  encoding               |  newcaps
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by nejucomo):

 A natural starting place for threat modeling attacker capabilities would
 be the operator of a single storage node.  Here's how to get started in
 your career of blackmailing `LAFS` users:

 1. run a storage node and use `find`, `ls`, and the like to examine the
 filesystem metadata on shares. (This could give sizes, creation times,
 modification times, access times.)
 1. examine local share contents using any tools at your disposal. (What
 can this tell an attacker about shares? Serial numbers? Signing keys?
 merkle tree roots?)
 1. turn up logging, and modify the storage node code to log protocol-level
 requests data of interest. (This could give client IPs, more precise
 timing information, range requests on shares.)

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