From: Lars Ingebrigtsen <larsi@gnus.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: 41659@debbugs.gnu.org
Subject: bug#41659: 28.0.50; smime: encryption uses now base64, message not readable
Date: Mon, 20 Jul 2020 13:07:26 +0200 [thread overview]
Message-ID: <87pn8qh2c1.fsf@gnus.org> (raw)
In-Reply-To: <87h7u2v4br.fsf@mat.ucm.es> (Uwe Brauer's message of "Mon, 20 Jul 2020 13:00:40 +0200")
Uwe Brauer <oub@mat.ucm.es> writes:
> No sorry this is *not* the problem. I recall we had this discussion and
> you closed a similar bug, because I incorrectly stated it is about smime
> signed messages. It is not.
>
> It is about encrypted+signed non-ascii message.
>
> This is why I needed Jens Lechtenberger to jump in because he is one of
> the few gnus users with a smime certificate.
>
> So in order to reproduce and debug it, I suggest you either
>
> 1. Get a free smime certificate, there are still some, valid for
> some month. I could look it up for you.
>
> 2. Or maybe your government provides you with one. This is,
> surprisingly, what the spanish goverment does, and I use this
> certificate, among other this for email encryption and signing.
Oh, yeah, this is now starting to sound vaguely familiar. :-)
Hm... I do seem to recall ... getting an smime certificate? Or did I
just try to and fail? Er... If I had gotten a certificate, where would
I have put it? :-)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-07-20 11:07 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pn8qh2c1.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=41659@debbugs.gnu.org \
--cc=oub@mat.ucm.es \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.