From: Andreas Fuchs <asf@void.at>
Subject: Re: opportunistic PGP encryption/signing
Date: Fri, 27 Sep 2002 10:04:43 +0200 [thread overview]
Message-ID: <E17uq79-0006v4-00@eris.void.at> (raw)
In-Reply-To: <86ofakbr6w.fsf@duchess.twilley.org>
[-- Attachment #1.1: Type: text/plain, Size: 645 bytes --]
On 2002-09-26, Jack Twilley <jmt+usenet@twilley.org> wrote:
> dme> - all outgoing mail is encrypted if I have a key for the
> dme> receiving party/parties,
>
> Other bbdb entries have tags requiring encryption. I have not yet
> written a script to associate keys with bbdb entries or to traverse my
> key-ring and set the related encryption tag in the bbdb entries, but
> it's on my list.
I've done such a thing, but it is really buggy (the regex matching names
requires special care - it matches a " " at the end too many). Please
don't use the module unmodified, it could might ruin your .bbdb
(i.e. add a lot of dupes).
[-- Attachment #1.2: bbdb-gpg-ring.el --]
[-- Type: application/emacs-lisp, Size: 1535 bytes --]
[-- Attachment #1.3: Type: text/plain, Size: 1256 bytes --]
I hope that helps (even though there are no comments (-;).
> dme> - the key used for signing/encryption can be determined by a
> dme> hook function (such as something added to message-send-hook,
> dme> which I currently use for choosing a From: address,
> dme> signature, etc.).
>
> This would be pretty simple, but it's not something I would ever use
> so I never implemented it.
I don't think it would be very useful for people who have more than one
private key in their ring for one address (people like me, for example,
who created a key with a very old version of gpg and then created a new
one when the security advisory was posted).
> dme> Coupled with interfaces for acquiring keys, etc. this would be
> dme> great.
>
> Something that snarfed keys and updated the bbdb would probably
> complete my needs in this case.
Yow, that would be really great.
> dme> Does it exist ?
>
> If you think my bbdb-pgp changes would suit your needs, let me know
> and I'll post them here.
Please do. I hope you're using the mml-secure-message-.*-pgpmime stuff?
Have fun,
--
Andreas Fuchs, <asf@acm.org>, asf@jabber.at, antifuchs
Was I helpful? Let others know:
http://svcs.affero.net/rm.php?r=antifuchs
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2002-09-27 8:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 15:27 dme
2002-09-26 17:23 ` Jack Twilley
2002-09-27 8:04 ` Andreas Fuchs [this message]
2002-09-27 0:17 ` Daniel Pittman
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=E17uq79-0006v4-00@eris.void.at \
--to=asf@void.at \
/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).