From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: Encryption vs. Gcc
Date: Wed, 04 Sep 2013 22:07:44 +0200 [thread overview]
Message-ID: <87d2oo9wq7.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <87fvtku3u3.fsf@gnu.org>
ludo@gnu.org (Ludovic Courtès) writes:
> Anyway, a more ideal solution for Gcc: would be this: if the message is
> encrypted, then keep a copy encrypted with the sender’s public key
> (rather than clear-text); otherwise keep a copy as is.
I am using:
hidden-encrypt-to 0xMYKYHERE!
in my ~/.gnupg/gpg.conf to achieve this.
From gpg(1):
--hidden-encrypt-to name
Same as --hidden-recipient but this one is intended for use in the
options file and may be used with your own user-id as a hidden
"encrypt-to-self". These keys are only used when there are other
recipients given either by use of --recipient or by the asked user
id. No trust checking is performed for these user ids and even dis‐
abled keys can be used.
Best regards,
Adam
--
"It's not denial. I'm just very selective about the Adam Sjøgren
reality I accept." asjo@koldfront.dk
next prev parent reply other threads:[~2013-09-04 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 13:13 Ludovic Courtès
2013-09-04 18:41 ` Philipp Haselwarter
2013-09-06 13:02 ` Ludovic Courtès
2013-09-04 20:07 ` Adam Sjøgren [this message]
2013-09-06 13:10 ` Christopher Schmidt
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=87d2oo9wq7.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=ding@gnus.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).