From: jens.lechtenboerger@fsfe.org
Cc: ding <ding@gnus.org>
Subject: Re: S/MIME verification, marking of encryped
Date: Sun, 11 Oct 2015 10:17:54 +0200 (CEST) [thread overview]
Message-ID: <1562862440.6587.1444551474352.JavaMail.open-xchange@ox1app> (raw)
In-Reply-To: <smuzizraruj.fsf@linuxpal.mit.edu>
Greg Troxel <gdt@lexort.com> writes:
> jens.lechtenboerger@fsfe.org writes:
>
> Your blog post conflates the common PKI model and the S/MIME standard
> itself
I hope not. I explain that you need a notion of trust, and I also
mention the case of the monopoly.
> - which I realize is how normal people come to this.
Come to what?
> Some organizations use S/MIME but only configure their own CAs as
> trust anchors. This is quite sane. But I agree that that vast CA
> list is goofy and inflicted on most people.
Using just your own CA conflicts with the decentralized model of e-mail.
>> My recommendation is to stay away from openssl. Use gpgsm.
>
> So perhaps the defaults should be flipped in gnus, so that epg/gpgsm is
> used, throwing an error if not found (or silently not decoding merely
> signed?), unless someone has explicitly asked for the openssl version?
Yes, I agree. Actually, I plan to propose that later this month.
Currently, I’m working on the refactoring of encryption related code in
Gnus that I proposed more than a year ago on this list.
>> My advice is to go for OpenPGP :-)
>
> You vastly overestimate my status as world dictator :-)
Too bad. Definitely worth a try.
Best wishes
Jens
next prev parent reply other threads:[~2015-10-11 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 17:23 Greg Troxel
2015-10-10 7:20 ` jens.lechtenboerger
2015-10-10 11:24 ` Greg Troxel
2015-10-11 8:17 ` jens.lechtenboerger [this message]
2015-10-13 22:05 ` Greg Troxel
2015-10-11 11:26 ` 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=1562862440.6587.1444551474352.JavaMail.open-xchange@ox1app \
--to=jens.lechtenboerger@fsfe.org \
--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).