unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Verifying signed mail in Gnus
Date: Wed, 02 Nov 2022 22:52:47 +0200	[thread overview]
Message-ID: <875yfxdqow.fsf@thaodan.de> (raw)
In-Reply-To: <87wn8fzs58.fsf@mat.ucm.es> (Uwe Brauer's message of "Mon, 31 Oct 2022 20:53:39 +0100")

Uwe Brauer <oub@mat.ucm.es> writes:

>    1. The public key interchange is so much simpler (but see below
>     risks), since the public key is always embedded in your signature

There are movement on going to improve that notably autocrypt. The only
downside is that email clients in general aren't that good or good to
adapt to new standards.

>     2. SMIME support is basically shipped in most MTA, moreover the key
>      generation is also much simpler for newbies.

What I see quite often that PKCS#11 is not always implemented in all
programs that use similar certificates as SMIME where as for pgp it was
never an issue to use hardware tokens since most programs us gpg.

>     3. IF you have the all the relevant CAs installed (which might not
>       always be the case), the authentification is done automatically,
>       for GNU/Linux for example by the ggpsm program which is used
>       usually by emacs.

I think that is also possible with pgp but it depends on your pgp
program and your email program. Clients such as Kmail can do these
things automatically I think.


>     4. Some government agencies already provide SMIME keys for their
>        residents, for example Spain.

Some governments or agencies support pgp, quite often security researchs
offer it.
In Germany some of parts justice system support pgp, although I haven't
seen them distribute their keys on a keyserver.

Br,

Björn



  reply	other threads:[~2022-11-02 20:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 10:24 Verifying signed mail in Gnus Angel de Vicente
2022-10-31 11:48 ` Akib Azmain Turja
2022-10-31 12:30   ` Angel de Vicente
2022-10-31 17:04     ` Akib Azmain Turja
2022-10-31 19:53     ` Uwe Brauer
2022-11-02 20:52       ` Björn Bidar [this message]
2022-11-02 23:53         ` Tomas Hlavaty
2022-11-03  5:24           ` Björn Bidar
2022-11-03  8:53             ` Tomas Hlavaty
2022-10-31 19:18   ` GH

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=875yfxdqow.fsf@thaodan.de \
    --to=bjorn.bidar@thaodan.de \
    --cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).