From: Andreas Fuchs <asf@void.at>
Subject: Re: mml-secure-message-... functions should work together?
Date: Thu, 24 Jan 2002 18:43:33 +0100 [thread overview]
Message-ID: <E16TnuP-00050L-00@eris.void.at> (raw)
In-Reply-To: <87n0z3iyw8.fsf@paradoxical.net>
[-- Attachment #1: Type: text/plain, Size: 563 bytes --]
Today, Josh Huber <huber@alum.wpi.edu> wrote:
> Well, with gpg.el anyway selecting "encrypt" actually signs the
> message as well...
Hm, a test I performed did not tell me so. The message I sent myself was
just encrypted, and not signed. This is strange...
> I agree though -- we should allow the user to choose if they would
> like to sign. (although, encrypting without signing should not be the
> default.)
I'd fully agree to the default if it did actually it sign my messages (:
--
Andreas Fuchs, <asf@acm.org>, asf@jabber.at, antifuchs
[-- Attachment #2: Type: application/pgp-signature, Size: 239 bytes --]
next prev parent reply other threads:[~2002-01-24 17:43 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
2002-01-24 11:46 ` Andreas Fuchs
2002-01-24 14:53 ` Josh Huber
2002-01-24 17:43 ` Andreas Fuchs [this message]
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=E16TnuP-00050L-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).