Gnus development mailing list
 help / color / mirror / Atom feed
From: Florian Weimer <fw@s.netic.de>
Subject: Re: MML, message-send-hook and automatically GnuPG-signing messages.
Date: 18 Jan 2000 12:39:12 +0100	[thread overview]
Message-ID: <87n1q38v8f.fsf@deneb.cygnus.argh.org> (raw)
In-Reply-To: Jonas Steverud's message of "18 Jan 2000 11:35:19 +0100"

Jonas Steverud <d4jonas@dtek.chalmers.se> writes:

> > <#multipart type=signed>
> [...]
> 
> How can I ensure that this will be expanded _last_? Signing and
> encrypting demands that it is done last.

Look at the code.  It compiles the contained MML directives and, as a
result, gets the raw representation of the contained parts.  After that,
you can calculate signatures, encrypt it, in short: do whatever you want.

I don't think an additional hook is required, in fact, I would be
surprised. ;)

You only need additional data structures for decrypting and verifying
signatures.

But the whole discussion is unnecessary at the moment.  There is no
safe way to invoke PGP or GnuPG from Emacs on most systems (at least
on all I tested except Solaris), so it's probably not very wise to use
Mailcrypt and similar packages on a multi-user machine.




  parent reply	other threads:[~2000-01-18 11:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <wtnpuv5wurx.fsf@licia.dtek.chalmers.se>
2000-01-16  8:14 ` Florian Weimer
     [not found]   ` <wtn3drwabws.fsf@licia.dtek.chalmers.se>
2000-01-17 21:42     ` Kai Großjohann
2000-01-18  5:26     ` Florian Weimer
     [not found]       ` <wtnr9ffbrbs.fsf@licia.dtek.chalmers.se>
2000-01-18 11:39         ` Florian Weimer [this message]
     [not found]           ` <wtn1z7f8rl8.fsf@licia.dtek.chalmers.se>
2000-01-18 13:50             ` Florian Weimer
     [not found]               ` <wtn7lh7id3y.fsf@licia.dtek.chalmers.se>
2000-01-18 19:12                 ` Florian Weimer

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=87n1q38v8f.fsf@deneb.cygnus.argh.org \
    --to=fw@s.netic.de \
    /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).