See the github repo https://github.com/zweidenker/Cryptography for the up to date project.

the Cryptography repository from squeaksource.

Overview

This repository is used for the Cryptography Team development. For infomration see the wiki and / or sign up for our news list at http://lists.squeakfoundation.org/mailman/listinfo/cryptography If you would like to volenteer please do so by sending an email to ron@USMedRec.com or drop us a line on the list.

Cryptology Team Wiki

The main goal is to provide the tools necessary so that anyone can successfully implement current cryptography into their applicaiton.

This page is a work in progress

Currently we are assembling a team, and setting team goals. for information contact: Ron@USMedRec.com Also see our mailing list: http://lists.squeakfoundation.org/mailman/listinfo/cryptography

Cryptography Team Notes

Cryptography goals

1. Identify and isolate Cryptographic classes and define SM package for base image classes.
2. Maintain Current Cryptography Standards in the image.
3. Make sure that the external package stays current with image implementations. (SHA1 and SecureHashAlgorithm are copies of each other but there were differences in implementations. I'm not sure why we need both but there you are.).
4. Fix errors in Cryptography in package or in image like ThrityTwoBitRegister, The byteArray appears to be implemented backwards. We will need rights to make/change assignments in Mantis.

5. Complete Cryptographic Module Validation Program (CMVP) through the OpenSSL Federal Information Processing Standard (FIPS) Certification Process. http://csrc.nist.gov/cryptval/140-2.htm

   5.1 Identify Experts in Group (recruit new members?)

   5.2 Find repository and define structure for documentation.

   5.3 Document current frameworks

   5.4 Develop new designs, following design goals (tbd through open discussions) and document new framework.

   5.5 Expert Design Review and Implementation recursively until code complete

   5.6 Identify Team Leaders to walk our project through OpenSSL FIPS Cert Process

   5.7 Raise Money for Cert Process

   5.8 Complete Certification, Publicize results

   5.9 Offer Reward for anyone that breaks code

   5.10 Set up review committee that reviews implementations (for a fee) and helps others get certified using our code.

6. Research and add cryptography as necessary to stay current with cryptographic changes in the industry.
7. Support CACert.
8. Integrate Signatures and Encryption into Email Packages.
9. Write Security Articles for cross promotion with squeak news team (and publish some articles outside this group for squeak promotion).
10. Start Cryptography list for people using the internal or external package for cryptographic news and alerts, or changes in implementations planned so that consumers of the cryptographic code can understand what changes are needed to integrate new code.
11. Support PGP

12. Fix PKI

    PKI Tasks

    12.1) Review Current Implementation

    12.2) Isolate classes and convert to Monticello Format

    12.3) Develop / Round out Streaming Protocol (similar to SSH or SSL)

    12.3a) Add State machine

    12.3b) Add PKI/Diffie Hellman Handshaking

    12.4) Project path:

    12.4a) ASN1 implementation

    12.4a.1) Compare Cincom's non comercial version to the Squeak Asn1 implementation

    12.4a.2) Port Cincom's non comercial version features or entire package if necessary

    12.4b) x509 version3

    12.4c) deffie helman (see 12.3b)

    12.4d) AES, 3DES and various other block and symmetric ciphers.

    12.4e) (see 11).

    12.4f) ssl / tls version 3 of ssl.

13. Assess adding SFTP

14. Review ANS1 (and voip or other high profile implementations for reference implementation)
15. Support and Develop SUnit cases for everything.