From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Status of GPG support?
Date: Thu, 13 Dec 2007 17:01:24 -0800 [thread overview]
Message-ID: <1197593643-sup-6305@south> (raw)
In-Reply-To: <1197324612-sup-4789@south>
Excerpts from William Morgan's message of Mon Dec 10 14:13:42 -0800 2007:
> I will send an announcement when it's in.
I've committed a patch to add sign, encrypt, and sign+encrypt
capability. As with decryption and signature verification, this is gpg-
specific, and relies on gpg-agent for all password interactions. I don't
really want to get into the business of password management.
I need to add some mechanics for determining which setting is pre-
selected on a per-message basis. This will almost certainly be a hook.
Other than that, is should be basically functionally complete.
I did add one config option: :discard_snippets_from_encrypted_messages,
which defaults to false. If this option is set to true, snippets that
were generated from encrypted content will not be stored in the index.
This is a limited security measure, because someone with access to the
Ferret index can recover the contents of the message in several ways
(that's the problem with the basic operation being full-text search!),
but this eliminates the most trivial way of getting encrypted message
content. It also means that the snippet for a message won't show up in
thread-index-mode until you load the message and enter in the password.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2007-12-14 1:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 21:49 Magnus Therning
2007-12-10 22:13 ` William Morgan
2007-12-14 1:01 ` William Morgan [this message]
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=1197593643-sup-6305@south \
--to=wmorgan-sup@masanjin.net \
/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