Gnus development mailing list
 help / color / mirror / Atom feed
From: "Georg C. F. Greve" <greve@gnu.org>
Subject: Crypto-MIME in GNUS
Date: 10 Apr 2001 10:52:56 +0200	[thread overview]
Message-ID: <m34rvx3zmf.fsf@reason.gnu-hamburg> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1425 bytes --]

Hi guys,

since I have received so much help revising my mail schemes and once
again I'm very satisified with how things work, I thought I should
contribute something that some people might useful. I don't think I
posted this here, yet.

There is a lot of encrypted mail coming in/going out here and I needed
gnus to be able to handle it completely transparent and MIME
compliant. Unfortunately there were some problems.

The biggest problem was that the gnus crypto function didn't work
since it gave mailcrypt the buffer to encrypt that didn't contain
headers so mailcrypt had no way to determine who to encrypt it
for. Also when I got it to work half-way I realized that CC and BCC
were ignored.

Also I wanted a nice way to determine whether to encrypt or sign that
I could toggle while composing the mail.

AND I wanted it to interface with the BBDB. I havethe "pgp-mail" field
that if set to sign/encrypt automatically signs/encrypts everything to
this person.

What is also nice is an easy way to include public keys into the mail
with correct MIME type. The solution I have is ugly but I didn't have
time to think about something better and for now it works.

The following code fixes/does all this. It is probably more a cludge
than a solution but it does the job and I have been using it
successfully for a few months now. Maybe someone will find it useful.

Personally I have set:

[-- Attachment #1.2: Type: application/emacs-lisp, Size: 198 bytes --]

[-- Attachment #1.3: Type: text/plain, Size: 241 bytes --]

which means that when writing mail, F1 sets it to sign, F2 to encrypt
and F4 removes the tag. F3 (encrypt with recipients) doesn't work for
some reason... didn't have time to investigate it further.

Regards,
                Georg



[-- Attachment #1.4: The crypto-related routines in my .gnus --]
[-- Type: application/emacs-lisp, Size: 9591 bytes --]

[-- Attachment #1.5: Type: text/plain, Size: 226 bytes --]


-- 
Georg C. F. Greve                                       <greve@gnu.org>
Free Software Foundation Europe	                 (http://fsfeurope.org)
Brave GNU World	                           (http://brave-gnu-world.org)

[-- Attachment #2: Type: application/pgp-signature, Size: 268 bytes --]

             reply	other threads:[~2001-04-10  8:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-10  8:52 Georg C. F. Greve [this message]
2001-04-10 10:50 ` Simon Josefsson
2001-04-10 13:27   ` Georg C. F. Greve
2001-04-10 13:23     ` Simon Josefsson
2001-04-12 10:33       ` Georg C. F. Greve
2001-04-12 11:27         ` Florian Weimer
2001-04-10 14:19     ` Josh Huber
2001-04-13 13:10   ` Georg C. F. Greve

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=m34rvx3zmf.fsf@reason.gnu-hamburg \
    --to=greve@gnu.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).