Qed/Ryan et al,
Yes you have to pass the filter a seed to run the encryption but I have to admit I don't know how it decrypts the code automagically. Ben Mord and I took this offline and he likened the resulting block to a fancy lock with the key in it b/c the seed I passed to start the encryption has to be available to Perl when it interprets my code. I suspect you would agree. Ben has a similar need for automated decryption as I do but does the decryption via a specialized computer dedicated to the task whose access and config is tightly controlled - see his response.

Do either of you guys do automated decryption? This doesn't seem to be addressed in the FAQ - just automated signing. I'm open to suggestions.

btw - am I screwing up my responses? There seem to be mult. threads being generated. I'm just hitting reply.

John














Qed wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

On 04/07/2006 09:56 PM, John M Church wrote:
Not sure if "mask the passphrase in a non-obvious way" does justice to
encrypting it with a filter and strong algorithm - ref.
<http://search.cpan.org/~beatnik/Filter-CBC-0.09/CBC.pm>.  Were you
thinking I was only hiding it in clear text?
Simply I don't know anything about this perl module, but where the key
to decrypt the passphrase would be stored? If such a safe place exists
why not using it directly for the gpg passphrase?
- --

 Q.E.D.

ICQ UIN: 301825501
OpenPGP key ID: 0x58D14EB3
Key fingerprint: 00B9 3E17 630F F2A7 FF96  DA6B AEE0 EC27 58D1 4EB3
Check fingerprints before trusting a key!


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQFENt6xH+Dh0Dl5XacRA53ZAJ9cgwj5/gJGetJ7atqPWKLX/hfTBACfXIGi
1djGAaNrtAzKILj1YqrjU1c=
=emRC
-----END PGP SIGNATURE-----


_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Reply via email to