unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
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 13:52:01 +0200	[thread overview]
Message-ID: <86ppbhrx9a.fsf@yandex.ru> (raw)

And has been doing that ever since NSM patches were installed, IIRC.

Am I doing something wrong?

Looks like this:

Certificate information
Issued by:          news.gmane.org
Issued to:          Gmane
Hostname:           news.gmane.org
Public key:         RSA, signature: RSA-SHA1
Protocol:           TLS1.0, key: DHE-RSA, cipher: AES-128-CBC, mac: SHA1
Security level:     Weak
Valid:              From 2011-12-04 to 2014-12-03


The TLS connection to news.gmane.org:nntp is insecure for the
following reasons:

certificate signer was not found (self-signed)
certificate could not be verified


In GNU Emacs 25.0.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.10.8)
 of 2014-12-18 on axl
Repository revision: 18d4bdf135524f33173caa2ef2164345bd09017d
Windowing system distributor `The X.Org Foundation', version 11.0.11501000
System Description:	Ubuntu 14.04.1 LTS





             reply	other threads:[~2014-12-18 11:52 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-18 11:52 Dmitry Gutov [this message]
2014-12-18 14:49 ` bug#19404: 25.0.50; Gnus shows self-signed certificate warning when connecting to Gmane 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
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=86ppbhrx9a.fsf@yandex.ru \
    --to=dgutov@yandex.ru \
    --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).