I think your structure is pretty logical for the src folder. I think we may additionally want to add a key management folder within src that would contain different key management that we could be instantiated and they would work interchangeably (such as using html5 storage and also a dropbox connector..)
I think the one thing we might want to break off is the incorporation of the implementations (in your case the gmail extension code), just because the goal is to create something of a universal library. If I look at your code outline correctly it looks like the objective is to create a universal webmail extension? I'm curious what you're envisioning for plugins and webmail API? I'm not quite sure I understand what we would need for an API for this that wouldn't just be direct calls to encrypt/decrypt/sign/key management calls that would be fairly generic? RFC822 is pretty old, I believe, how exactly are you combining it into reading with gmail? Overall though, I think your work is well laid out and will definitely provide a good starting point. I'm excited. Thanks, Sean On Tue, Dec 6, 2011 at 8:19 AM, Carsten Wentzlow <[email protected]>wrote: > Hi! > ~~~ > > As Felix wrote we are currently restructuring the project to fit into a > common goal. I would like to suggest the following directory structure: > > plugins/ - Plugin API and subdirectories containing the plugin code > plugins/chrome/ - Plugin for chrome (current state) > webmail/ - Generic WebMail API (here We have to define a generic > API to be implemented by all webmail integrations) > webmail/gmail/ - Current gmail integration code > src/ - Main source folder for the openpgp implementation > (keyring, message, private / public key) > src/ciphers/ - Generic openpgp crypto interface > src/ciphers/asymmetric/ - DSA, RSA, Elgamal > src/ciphers/symmetric/ - AES, blowfish, CAST5, DES, twofish > src/ciphers/hash/ - Hash algorithms (sha*, ripe-md160, md5) > src/compression/ - Compression methods (currently none; ZIP, ZLIB Bzip2) > src/encoding/ - Encoding libs (base64, ascii armor format, emsa / > eme pkcs1) > src/packet/ - Openpgp packet implementation > src/type/ - Openpgp type objects (MPI, keyId, s2k) > src/util/ - Debugging, type conversion (string <-> array), checksum > calculation > lib/ - Libraries > lib/rfc822/ - I'm currently working on a RFC822 Message parser > which i use to parse message in gmail > doc/ - Documentation (currently i use JavaDoc) > config/ - Generic configuration API for all plugins. A use > would be able to choose on the used plugin which webmail integration is to > be used. > > Build targets would be the plugins for the browser. > > The src folder is structured like the current version of gpg4browsers js/ > folder containing the openpgp implementation. > > Please give some input. I may violate some common practice on github. > > regards, > carsten > > -- > > Recurity Labs GmbH | Carsten Wentzlow > http://www.recurity-labs.com | [email protected] > Wrangelstrasse 4 | Fon: +49 30 69539993-0 > 10997 Berlin | Mobil: +49 163 7007430 > Germany | PGP: AF3F 4C6C F80A 7C76 7DDE > | 39BF 83DD 3803 E163 4F45 > HRB 105213 B, Amtsgericht Charlottenburg, GF Felix Lindner > > > > _______________________________________________ > > http://openpgpjs.org >
_______________________________________________ http://openpgpjs.org
