r10 - 26 Oct 2004 - 16:04:53 - HeikkiToivonenYou are here: OSAF >  Projects Web  >  DevelopmentHome > SecurityFramework > CryptoSchedule

Schedule for Cryptography-related Work in Chandler

See CryptographicRequirements and CryptoDesign.

Scheduled in Bugzilla

Bugzilla


Historical...

0.X Release

  • Certificates. Andi depends on these at least partially for 0.3.16:
    1. Creation of X.509 certificates: 0.3.15 (May 4th), Medium
    2. Password protecting private keys: 0.3.15 (May 4th), Small
    3. The ability to forget certificates and start using new ones: 0.3.15 (May 4th), Medium
    4. Verifying of certificate thumbprints: 0.3.15 (May 4th), Medium
    5. API: 0.3.15 (May 4th), Medium
  • SSL. Andi depends on these at least partially for 0.3.18:
    1. Sharing over SSL: 0.3.17 (May 25th), Medium/Large
    2. Establishing friends network for sharing (implies exchanging certificates): 0.3.17 (May 25th), Large
  • Store all crypto-related things normally in files on the file systems (certificates, randseeds, keys, ...)
  • Work with Chandler-created certificates only
  • Concern: If we decide to adopt Twisted, it would require integrating M2Crypto into Twisted to replace PyOpenSSL. Medium.

0.Y Release

  1. Sharing over XMPP using encrypted and signed messages (using S/MIME, PKCS#7?)
  2. Sharing over email using S/MIME encrypted and signed messages
  3. Storing certificates and private keys in Chandler repository
  4. Work with certificates issued by real CAs

0.Z Release

  1. Secure replication of Chandler repository
  2. Certificate revocation checks for certificates that are signed by real CAs
  3. Documentation (parts of it should be done along the way, of course)
  4. Audit

-- HeikkiToivonen - 23 Feb 2004

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r10 < r9 < r8 < r7 < r6 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.