From: asjo@koldfront.dk (Adam Sjøgren)
To: info-gnus-english@gnu.org
Subject: Re: S/MIME with OpenSSL?
Date: Wed, 11 Nov 2015 17:12:10 +0100 [thread overview]
Message-ID: <87si4ch5wl.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87wptolvus.fsf@mat.ucm.es>
Uwe writes:
> Did you try once to convince computer how shall I say illiterate to
> use encryption?
I learned a long time ago not to try and impose my preferences on other
computer users.
> operations S/MIME PGP
> Inst of software no; included yes
I think you have some hidden assumptions about what software is used
here? Don't both S/MIME and PGP use external tools in Gnus?
> Installation of plugin no; included yes
Again, you must be assuming something about the software being used -
Gnus has built in support for both, right?
> generation of keypair no; ask for a yes
> certificate
This seems to be a negative for S/MIME: it is easy to generate a PGP
key. How do you generate an S/MIME certificate?
> interchange of public simply send a sign yes interchange
> keys message
I have never received or sent an S/MIME message, so it's hard to judge
this one. Does it mean that every S/MIME message includes the public key
of the sender? What prevents you from doing that with PGP-signed messages?
I've set up Gnus/GnuPG to automatically fetch keys for every person I
see a signature from, so there is nothing manual for me to do here.
Best regards,
Adam
--
"Probabilistic algorithms don't appeal to me. (This Adam Sjøgren
is a question of aesthetics, not practicality.) So asjo@koldfront.dk
later, I figured out how to remove the probability
and turn it into a deterministic algorithm."
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2015-11-11 16:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-08 16:15 Jens Lechtenboerger
2015-11-10 16:42 ` Uwe Brauer
2015-11-10 21:41 ` Adam Sjøgren
2015-11-11 9:38 ` Uwe Brauer
2015-11-11 16:12 ` Adam Sjøgren [this message]
2015-11-12 9:31 ` Uwe Brauer
2015-11-12 15:31 ` Adam Sjøgren
2015-11-13 18:55 ` Uwe Brauer
2015-11-14 15:37 ` Trust and public keys (was: S/MIME with OpenSSL?) Jens Lechtenboerger
2015-11-15 21:07 ` Trust and public keys Uwe Brauer
2015-11-16 21:15 ` Jens Lechtenboerger
2015-11-18 15:04 ` Uwe Brauer
2015-11-19 17:05 ` Jens Lechtenboerger
2015-11-22 18:09 ` [smime and gpg] (was: Trust and public keys) Uwe Brauer
2015-11-16 11:32 ` Trust and public keys Uwe Brauer
2015-11-12 19:20 ` S/MIME with OpenSSL? Peter Münster
2015-11-13 18:21 ` 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=87si4ch5wl.fsf@tullinup.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=info-gnus-english@gnu.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).