From: Ivan Shmakov <ivan@siamics.net>
To: 19404@debbugs.gnu.org
Subject: bug#19404: 25.0.50; Gnus shows self-signed certificate warning when connecting to Gmane
Date: Thu, 18 Dec 2014 19:10:48 +0000 [thread overview]
Message-ID: <87388cixjb.fsf@violet.siamics.net> (raw)
In-Reply-To: <m3egrwpyzr.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 18 Dec 2014 19:57:28 +0100")
>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>>>>> Eli Zaretskii <eliz@gnu.org> writes:
[…]
>> If the latter, can _we_ somehow distinguish between the two cases
>> and add some text to that effect?
> These are our translation to text from the GnuTLS error messages
> (which we have previously translated to symbols). I had hoped that
> the :not-ca case would help, but I've never seen it in the wild.
[…]
> if (EQ (status_symbol, intern (":self-signed")))
> return build_string ("certificate signer was not found (self-signed)");
> if (EQ (status_symbol, intern (":not-ca")))
> return build_string ("certificate signer is not a CA");
Presumably the former is returned when the certificate is signed
by an unknown CA, which /typically/ – but by no means
/necessarily/ – implies a self-signed certificate. It’s of
course possible for the peer’s certificate to be signed by a CA
not known (or not trusted) by the user.
The latter would mean that the signing party is not a CA. That
is: the signer’s own certificate lacks the CA flag. (The
certificate will be also the peer’s own one in the self-signed
case.)
[…]
--
FSF associate member #7257 http://boycottsystemd.org/ … 3013 B6A0 230E 334A
next prev parent reply other threads:[~2014-12-18 19:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 11:52 bug#19404: 25.0.50; Gnus shows self-signed certificate warning when connecting to Gmane Dmitry Gutov
2014-12-18 14:49 ` Lars Magne Ingebrigtsen
2014-12-18 15:00 ` Dmitry Gutov
2014-12-18 15:56 ` Eli Zaretskii
2014-12-18 16:06 ` Lars Magne Ingebrigtsen
2014-12-18 17:28 ` Eli Zaretskii
2014-12-18 17:53 ` Lars Magne Ingebrigtsen
2014-12-18 17:56 ` Eli Zaretskii
2014-12-18 18:57 ` Lars Magne Ingebrigtsen
2014-12-18 19:10 ` Ivan Shmakov [this message]
2014-12-18 20:30 ` Eli Zaretskii
2014-12-18 20:20 ` David Engster
2014-12-18 20:52 ` Eli Zaretskii
2014-12-18 21:40 ` David Engster
2014-12-18 21:50 ` David Engster
2014-12-18 22:04 ` Ivan Shmakov
2014-12-18 22:47 ` David Engster
2014-12-19 17:32 ` Ivan Shmakov
2014-12-19 8:28 ` Eli Zaretskii
2014-12-19 8:30 ` Eli Zaretskii
2014-12-19 12:11 ` Lars Ingebrigtsen
2014-12-19 12:20 ` Dmitry Gutov
2014-12-19 14:46 ` Eli Zaretskii
2014-12-19 14:40 ` Eli Zaretskii
2014-12-19 16:55 ` David Engster
2014-12-19 17:17 ` David Engster
2014-12-21 17:16 ` David Engster
2014-12-18 17:56 ` Dmitry Gutov
2014-12-20 14:17 ` Ted Zlatanov
2014-12-20 14:47 ` Eli Zaretskii
2014-12-20 21:44 ` Lars Ingebrigtsen
2014-12-24 13:11 ` Ted Zlatanov
2015-01-15 14:45 ` Ted Zlatanov
2015-01-16 0:23 ` Lars Magne Ingebrigtsen
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=87388cixjb.fsf@violet.siamics.net \
--to=ivan@siamics.net \
--cc=19404@debbugs.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.
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).