From: Werner Koch <wk@gnupg.org>
Subject: Re: 2002-01-08 / sending encrypted, but storing plain
Date: Wed, 08 Jan 2003 20:39:06 +0100 [thread overview]
Message-ID: <87u1gjzb1h.fsf@alberti.g10code.de> (raw)
In-Reply-To: <m3iswzfuwm.fsf@HayekA.Hayek.com> (Jochen_Hayek@ACM.org's message of "Wed, 08 Jan 2003 17:50:17 +0100")
On Wed, 08 Jan 2003 17:50:17 +0100, Jochen Hayek said:
> Usually if I send encrypted messages,
> I don't want to store them locally encrypted,
> as I can't re-decrypt them anyway.
The usual way to cope with this is by having a line
encrypt-to 12345678
in your gpg.conf (or options for old gpg versions), where 12345678 is
your key ID. This makes sure that all encrypted messages are in
addition encrypted to yourself. PGP has a similar option but I can't
recall it as it is too long ago that I used PGP 2.
BTW, mutt has an fcc-clear option which allows to store your copy in
plain - which is nice for not so confident messages. I have not yet
figured whether Gnus has something similar.
Salam-Shalom,
Werner
next parent reply other threads:[~2003-01-08 19:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3iswzfuwm.fsf@HayekA.Hayek.com>
2003-01-08 19:39 ` Werner Koch [this message]
2003-01-08 16:38 Jochen_Hayek
2003-01-08 22:22 ` Andreas Fuchs
2003-01-09 11:14 ` Werner Koch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87u1gjzb1h.fsf@alberti.g10code.de \
--to=wk@gnupg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).