-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 12 December 2001 13:12, mike ledoux wrote:
> I don't believe that is true in this case. For GPG to encrypt to a key, > it only needs the public key; to decrypt it needs both the private key > and the passphrase. As long as the machine doing the encrypting doesn't > have a copy of the private key, it should be quite difficult for someone > to automatically undo the encryption. > > If he were using symmetric encryption, then I'd agree with you. You are correct about the assymetric process. In fact we havecome up with a scheme which actually works. All of our machines are set up to use kmail as their primary email clients. All system mail is sent to a folder called "admin". A script in each machine's crontab runs the contents through gpg encrypting to my public key. when it is sent, the "folder" is replaced with an index and file containing no messages, just so kmail doesn't "freak out". There are still a few rough edges such as what happens if we are encrypting the contents or or replacing the index when an new system message is retrieved by kmail from the queue. But I like to tinker with such problems. - -- Robin Lynn Frank Director of Operations Paradigm-Omega, LLC ============================================================ For security reasons, no attachments or HTML content will be accepted. ============================================================ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8GURhRl1xq0FBQGgRAgqyAKCJqQlyXuHsXYdmNQsY9kmEcrqWwACgiFwZ WjEWBMbWhceT7+VrvCmzY4E= =kwny -----END PGP SIGNATURE-----
