From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: mml-secure-message-... functions should work together?
Date: Thu, 24 Jan 2002 12:29:45 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.44.0201241229020.14891-100000@slipsten.extundo.com> (raw)
In-Reply-To: <E16TgqI-00021Z-00@eris.void.at>
On Thu, 24 Jan 2002, Andreas Fuchs wrote:
> The current (CVS of today) message behaviour when using
> mml-secure-message-encrypt-... and mml-secure-message-sign-... is to
> toggle between mode=signed and mode=encrypted.
>
> WIBNI the functions complement each other, so that one can both encrypt
> and sign a message? Making mml-secure-message behave more like
> mml-secure-part would do the trick, I think.
Maybe a new "signencrypt" (or encryptsign? :-)) mode would do it?
next prev parent reply other threads:[~2002-01-24 11:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 10:10 Andreas Fuchs
2002-01-24 11:29 ` Simon Josefsson [this message]
2002-01-24 11:46 ` Andreas Fuchs
2002-01-24 14:53 ` Josh Huber
2002-01-24 17:43 ` Andreas Fuchs
2002-01-24 17:55 ` Josh Huber
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=Pine.LNX.4.44.0201241229020.14891-100000@slipsten.extundo.com \
--to=jas@extundo.com \
--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).