From: Uwe Brauer <oub@mat.ucm.es>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Uwe Brauer <oub@mat.ucm.es>, 41659@debbugs.gnu.org
Subject: bug#41659: 28.0.50; smime: encryption uses now base64, message not readable
Date: Thu, 23 Jul 2020 16:36:42 +0200 [thread overview]
Message-ID: <87zh7q9u2t.fsf@mat.ucm.es> (raw)
In-Reply-To: <87zh9mj5r1.fsf@mat.ucm.es>
[-- Attachment #1: Type: text/plain, Size: 556 bytes --]
>>> "LI" == Lars Ingebrigtsen <larsi@gnus.org> writes:
> OK, I now managed to send an S/MIME part to myself, apparently. (The
> interface isn't very er good -- when I was messing with this and pressed
> "cancel" in the pin entry, Message still sent the message...)
> In any case, I can't reproduce the bug. Looks fine to me:
> [[S/MIME Signed Part:Good signature from 9BF9CD19B5F45D8C2D0E6DF44A44812B553ACE6D /CN=larsi@gnus.org (trust full)]]
> This is ánother test.
The point is encrypted+signed mail with other users
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2020-07-23 14:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 7:17 bug#41659: 28.0.50; smime: encryption uses now base64, message not readable Uwe Brauer
2020-06-03 11:58 ` bug#41659: [bisect: found the culprits] (was: bug#41659: 28.0.50; smime: encryption uses now base64, message not readable) Uwe Brauer
2020-06-05 16:01 ` bug#41659: [ASCII is ok] (was: bug#41659: [bisect: found the culprits]) Uwe Brauer
2020-06-10 15:49 ` bug#41659: [ASCII is ok] Uwe Brauer
2020-07-20 10:39 ` bug#41659: 28.0.50; smime: encryption uses now base64, message not readable Lars Ingebrigtsen
2020-07-20 11:00 ` Uwe Brauer
2020-07-20 11:07 ` Lars Ingebrigtsen
2020-07-20 11:12 ` Lars Ingebrigtsen
2020-07-20 11:15 ` Uwe Brauer
2020-07-23 14:31 ` Lars Ingebrigtsen
2020-07-23 14:33 ` Lars Ingebrigtsen
2020-07-23 14:35 ` Uwe Brauer
2020-07-23 14:36 ` Uwe Brauer [this message]
2020-07-23 14:43 ` Lars Ingebrigtsen
2020-07-23 14:45 ` Lars Ingebrigtsen
2020-07-23 14:55 ` Uwe Brauer
2020-07-23 15:04 ` Lars Ingebrigtsen
2020-07-23 15:14 ` Lars Ingebrigtsen
2020-07-23 15:19 ` Uwe Brauer
2020-07-23 16:06 ` Uwe Brauer
2020-07-23 17:45 ` Eli Zaretskii
2020-07-24 14:39 ` Lars Ingebrigtsen
2020-07-24 15:10 ` Uwe Brauer
2020-07-24 15:15 ` Lars Ingebrigtsen
2020-07-24 15:26 ` Uwe Brauer
2020-07-24 15:29 ` Lars Ingebrigtsen
2020-07-24 15:31 ` Uwe Brauer
2020-07-23 15:17 ` Uwe Brauer
2020-07-23 15:20 ` Lars Ingebrigtsen
2020-07-23 15:28 ` Uwe Brauer
2020-07-23 16:16 ` Uwe Brauer
2020-07-20 11:19 ` Uwe Brauer
2020-07-22 7:29 ` Uwe Brauer
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zh7q9u2t.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=41659@debbugs.gnu.org \
--cc=larsi@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).