So, I've been thinking about this a bit and I think the ideal situation would be to have openpgp.js implement worker threads so that the public api of encrypting/decrypting would stay pretty much the same except for the addition of callback methods.
I think the best places to break it down are between the higher level process and the encryption/decryption mechanism. Initially my thought was to have a wrapper around all types of the packet objects, however I think this is largely unnecessary. Since the vast majority of encryption effort is in the encrypted integrity data packet (tag 18), and the vast majority of decryption effort is in the encrypted session key packet (tag 3), I think it makes most sense to focus on these first. I don't think it makes sense to have the keyring run in a thread of sorts, so the only window issue I think is the window.crypto problem. I believe the way to solve this is have the root openpgp.js call listen for messages and pass back secure randoms from the window as is necessary. (I'm not sure on the overhead this will add but perhaps it will be best to do this in large chunks). Thoughts everyone? Carsten? Sean On Sun, Feb 12, 2012 at 6:13 AM, Alex (via OpenPGP.js) <[email protected]>wrote: > Hi, > > On 12.02.2012, at 09:47, Fabio Pietrosanti (naif) wrote: > > Alex, Sean, you're the OpenPGP guru guys, what do you think on it? > > I think Carsten is *the* OpenPGP(.js) guru ;) Also I appreciate your > efforts, I agree that it's very useful to modularize the lib into a web > worker, and I'm currently on vacation w/o good Internet access ;) > > Best regards, Alex > > > _______________________________________________ > > http://openpgpjs.org >
_______________________________________________ http://openpgpjs.org
