Re: Encrypting incoming messages with GnuPG
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/09/09 17:42, Dave Patterson wrote:
> * Harry Rickards <hrickards@l33tmyst.com> [2009-05-09 11:14:14 +0100]:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> I was wondering if anyone knew of a way, perhaps using /etc/aliases, so
>> that all incoming mail addressed to my username (hrickards) is encrypted
>> with *my* public key, so that when I read it only I can read it using
>> *my* private key. If the mail was signed or encrypted beforehand, it
>> could then be decrypted with my private key as usual.
>>
>
> Hmm. So, we're looking at encrypting mails as they come in, prior to
> disk write, in a format that you, and only you, can later decrypt them,
> preferably using gpg. I don't care why, it's an intereѕting problem.
>
> Local storage remains secure. At least that's what I think is the
> intention.
>
> Outside of using some disk encryption system like this:
>
> <http://www.debianhelp.org/node/15244>
>
> I'd try to pipe the mail fetchmail, procmail (pipe to
> encryptionscrypt,write-encrypted-email-to-disk)
>
> Remembering procmail only functions as a gate, and does not write the
> mail to disk until told to, and neither does fetchmail
> (or getmail or retchmail).
>
> script should be very simple:
>
> gpg -e -r yourusergpgidhere themessage
>
> Build from that command.
>
> Trick is to not write to disk prior to encryption.
>
Uh, huh. Thanks for the tips, I'll try to come up with something from that.
- --
Many thanks
Harry Rickards (a.k.a l33tmyst)
- -----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GAT/GCM/GCS/GCC/GIT/GM d? s: a? C++++ UL++++ P- L+++ E--- W+++ N o K+
w--- O- M- V- PS+ PE Y+ PGP++ t 5 X R tv-- b+++ DI D---- G e* h! !r y?
- ------END GEEK CODE BLOCK------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkoFt9sACgkQ1kZz3mRu0Gq4XACdFKoCpfGYTN5rLfVUQWCv211w
v2kAoKL6WHKi+rioN31X4pLvBcLmAVFy
=d/Vr
-----END PGP SIGNATURE-----
Reply to: