Folks, Domenic Steinitz has contributed some crypto code (see attachment and msg below). According to our draft hierarchy, there is a place in the hierarchy reserved for crypto libraries: FileFormat.Encryption (see http://www.haskell.org/~simonmar/lib-hierarchy.html). Question 1: there's a comment next to 'FileFormat' which mentions that 'Codec' might be a more accurate name. It seems to me that 'Codec' would indeed be a better choice: many of the libraries under FileFormat are more like pure stream-transformers than file formats, and Codec encompasses both. What do people think about changing this? (there aren't any other implementations of libraries under FileFormat that I'm aware of). If FileFormat became Codec, then the existing FileFormat.Encoding looks a bit odd. But moving FileFormat.Encoding.Base64 up to Codec.Base64 (similarly for FileFormat.Encoding.Yenc) would seem to make sense. Question 2: what should the insides of the FileFormat.Encryption (or Codec.Encryption) hierarchy look like? Cheers, Simon -----Original Message----- From: Dominic Steinitz [mailto:dominic.steinitz@blueyonder.co.uk] Sent: 21 April 2003 18:47 To: Simon Peyton-Jones; Simon Marlow Cc: libraries-request@haskell.org Simon, Simon, Here's my first attempt at a crypto library. It compiles and I can run a test using ghc-inplace. The test checks with the example in http://www.itl.nist.gov/fipspubs/fip81.htm (except I couldn't find an example with PKCS#5 padding). I'm not sure what the next steps are. Dominic Steinitz