Well, your not using public private keypair encryption except for some key managment.. the actual encryption is going to be by a symmetric algorithm. Now, it's going to load the cpu.. the trick is to get a fast algorithm, so use AES-256 for your symmetric. That's a lot faster than triple des or blowfish. Second.. why pgp?? oh, well, it's "known". If you can do it, create a silicon drive for yourself and use that for your code, although I'd be more worried about the windows swap file than my data access, given what a pig windows is anyway.
Sux man to have to deal with that.. maybe you can dig some stuff out of bruce schneider's work and talk them out of "crypo-snake oil"
Slashdot Mirror
Well, your not using public private keypair encryption except for some key managment.. the actual encryption is going to be by a symmetric algorithm. Now, it's going to load the cpu.. the trick is to get a fast algorithm, so use AES-256 for your symmetric. That's a lot faster than triple des or blowfish. Second.. why pgp?? oh, well, it's "known". If you can do it, create a silicon drive for yourself and use that for your code, although I'd be more worried about the windows swap file than my data access, given what a pig windows is anyway. Sux man to have to deal with that.. maybe you can dig some stuff out of bruce schneider's work and talk them out of "crypo-snake oil"