Hi, I've been discussing ecc with Thomas. There are several options:
1. write our own 2. port just the ecc bits from google E2E 3. use E2E as a "kernel lib" and add an api wrapper to OpenPGP.js Our thinking is that 2 might be the fastest path to ecc, while 3 is a clear migration path to use only E2E ciphers in the future. It's been critized that OpenPGP.js is a mashup of many js-cipher from all around the internet and using code from one source might clean things up a little (without breaking the public api). We would also profit from their future developments (and more engineering recources than OpenPGP.js). Not to mention we would all be using one OpenPGP crypto lib, which should reduce maintenance and complexity while keeping up with Google and Yahoo. Thoughts? Tankred > Am 12.09.2014 um 22:20 schrieb "Fabio Pietrosanti (naif)" > <[email protected]>: > > yo, > > we've been discussing recently about the use of ECC Crypto into > OpenPGP.js in place of RSA/DSA. > > Are there any plan and/or quick hack to get it there? > > -- > Fabio Pietrosanti (naif) > HERMES - Center for Transparency and Digital Human Rights > http://logioshermes.org - http://globaleaks.org - http://tor2web.org > > _______________________________________________ > > http://openpgpjs.org > Subscribe/unsubscribe: http://list.openpgpjs.org _______________________________________________ http://openpgpjs.org Subscribe/unsubscribe: http://list.openpgpjs.org
