README file for Cracking_DES.zip
--------------------------------

In May 1998 the First Edition of a strange book was printed:

 Cracking DES
 Secrets of Encryption Research, Wiretap
 Politics & Chip Design

 by the Electronic Frontier Foundation
 ISBN: 1-56592-520-3
 Distributed by O'Reilly & Associates, Inc.,
 101 Morris Street, Sebastopol, CA 96472

On July 17, 1998 the EFF made a press release with the title
"EFF Builds DES Cracker that proves that Data Encryption
Standard is insecure; http://www.eff.org/descracker.html"

On Sunday July 26, the book was delivered to me. In the
upper right corner of the front page it says "Scan this book".

In general this would be a bit of a problem, however all source code
in the book, in the chapters 5, 6 and 7 is printed in a format that
should be familiar to anyone who owns a copy of the PGP 5.5 source
code books. (see ftp://ftp.pgpi.com/pub/pgp/5.5/books/ocr-tools.zip)

So those pages have been scanned, run through utilities like
'sortpages', 'repair' and 'unmunge' to produce the zip file
Cracking_DES.zip  I hope you will enjoy it.

I any reader ever want to publish a book with source code in
this way, a couple of advises are relevant.

- never print on a reduced size page. Either use the book format on
  A4 size or similar paper, or print significantly less lines per
  page. At the size of the EFF book, many spaces and semicolons
  had to be hand corrected.

- test scanning the book before publishing it. Anything that can
  reliably be scanned/OCRed at the author can be scanned at the
  reader.

- run your source code before formatting through a little script that
  . 'pretty prints' the text, doing indentation with ONLY TAB characters
  . discards any trailing white space
  . outside strings, REPLACES MULTIPLE SPACES WITH 'TAB' CHARACTERS
    (or omits them)
  . remembers that Omnipage Pro has remarkably bad results with lines
    of multiple equal characters. So avoid 'nastylines' like
    /*---------------------------------------------------------------- or
    ----------------------------------------------------------------*/ or
    /*****************************************************************
    Why not leave these comments at something like /* * * *

cheers,

teun