gdata.Crypto.Protocol.Chaffing | index /usr/local/google/home/afshar/src/external-gdata-release/google3/src/gdata/Crypto/Protocol/Chaffing.py

`This file implements the chaffing algorithm.
Winnowing and chaffing is a technique for enhancing privacy without requiring
strong encryption. In short, the technique takes a set of authenticated
message blocks (the wheat) and adds a number of chaff blocks which have
randomly chosen data and MAC fields. This means that to an adversary, the
chaff blocks look as valid as the wheat blocks, and so the authentication
would have to be performed on every block. By tailoring the number of chaff
blocks added to the message, the sender can make breaking the message
computationally infeasible. There are many other interesting properties of
the winnow/chaff technique.
For example, say Alice is sending a message to Bob. She packetizes the
message and performs an all-or-nothing transformation on the packets. Then
she authenticates each packet with a message authentication code (MAC). The
MAC is a hash of the data packet, and there is a secret key which she must
share with Bob (key distribution is an exercise left to the reader). She then
adds a serial number to each packet, and sends the packets to Bob.
Bob receives the packets, and using the shared secret authentication key,
authenticates the MACs for each packet. Those packets that have bad MACs are
simply discarded. The remainder are sorted by serial number, and passed
through the reverse all-or-nothing transform. The transform means that an
eavesdropper (say Eve) must acquire all the packets before any of the data can
be read. If even one packet is missing, the data is useless.
There's one twist: by adding chaff packets, Alice and Bob can make Eve's job
much harder, since Eve now has to break the shared secret key, or try every
combination of wheat and chaff packet to read any of the message. The cool
thing is that Bob doesn't need to add any additional code; the chaff packets
are already filtered out because their MACs don't match (in all likelihood --
since the data and MACs for the chaff packets are randomly chosen it is
possible, but very unlikely that a chaff MAC will match the chaff data). And
Alice need not even be the party adding the chaff! She could be completely
unaware that a third party, say Charles, is adding chaff packets to her
messages as they are transmitted.
For more information on winnowing and chaffing see this paper:
Ronald L. Rivest, "Chaffing and Winnowing: Confidentiality without Encryption"
http://theory.lcs.mit.edu/~rivest/chaffing.txt`

Classes

``

Chaff

class Chaff

``

`Class implementing the chaff adding algorithm.
Methods for subclasses:
_randnum(size):
Returns a randomly generated number with a byte-length equal
to size. Subclasses can use this to implement better random
data and MAC generating algorithms. The default algorithm is
probably not very cryptographically secure. It is most
important that the chaff data does not contain any patterns
that can be used to discern it from wheat data without running
the MAC.
`

Methods defined here:

__init__(self, factor=1.0, blocksper=1)
  `Chaff(factor:float, blocksper:int)
  factor is the number of message blocks to add chaff to,
  expressed as a percentage between 0.0 and 1.0. blocksper is
  the number of chaff blocks to include for each block being
  chaffed. Thus the defaults add one chaff block to every
  message block. By changing the defaults, you can adjust how
  computationally difficult it could be for an adversary to
  brute-force crack the message. The difficulty is expressed
  as:
  pow(blocksper, int(factor * number-of-blocks))
  For ease of implementation, when factor < 1.0, only the first
  int(factor*number-of-blocks) message blocks are chaffed.`

chaff(self, blocks)
  `chaff( [(serial-number:int, data:string, MAC:string)] )
  : [(int, string, string)]
  Add chaff to message blocks. blocks is a list of 3-tuples of the
  form (serial-number, data, MAC).
  Chaff is created by choosing a random number of the same
  byte-length as data, and another random number of the same
  byte-length as MAC. The message block's serial number is
  placed on the chaff block and all the packet's chaff blocks
  are randomly interspersed with the single wheat block. This
  method then returns a list of 3-tuples of the same form.
  Chaffed blocks will contain multiple instances of 3-tuples
  with the same serial number, but the only way to figure out
  which blocks are wheat and which are chaff is to perform the
  MAC hash and compare values.`

Data
`` |  | __revision__ = '$Id: Chaffing.py,v 1.7 2003/02/28 15:23:21 akuchling Exp $'