unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: David Engster <deng@randomsample.de>
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 23:47:44 +0100	[thread overview]
Message-ID: <87zjaklgmn.fsf@engster.org> (raw)
In-Reply-To: <87y4q4hawq.fsf@violet.siamics.net> (Ivan Shmakov's message of "Thu, 18 Dec 2014 22:04:53 +0000")

Ivan Shmakov writes:
>>>>>> David Engster <deng@randomsample.de> writes:
>>>>>> David Engster writes:
>
>  >> It *could* be self-signed. I don't know the best way in libgnutls to
>  >> detect this. You probably have to compare issuer and subject, or
>  >> similar.
>
>  > So my guess would be: use gnutls_x509_crt_get_dn2 or maybe
>  > gnutls_x509_crt_get_subject and compare to
>  > gnutls_certificate_get_issuer.  If equal -> self-signed.  But that
>  > could be wrong.  Best place is to ask on the GnuTLS list.
>
> 	If anything, it’s the respective public key fingerprints that
> 	are to be compared.

Sorry, I don't get it. Which respective public key fingerprints? There's
just one certificate.

-David





  reply	other threads:[~2014-12-18 22:47 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
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 [this message]
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=87zjaklgmn.fsf@engster.org \
    --to=deng@randomsample.de \
    --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).