From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: 19098@debbugs.gnu.org
Subject: bug#19098: 24.4.51; gnutls.c doesn't handle wildcard certificates
Date: Mon, 08 Dec 2014 21:11:49 +0100 [thread overview]
Message-ID: <m361dlsxyy.fsf@stories.gnus.org> (raw)
In-Reply-To: <878uj6c38m.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 19 Nov 2014 16:03:21 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> and is caused by the GNUTLS_CERT_INVALID flag. But I don't see a hint
> anywhere that it does not work with wildcard certs (you have to
> explicitly disable them, so the assumption is that they work by
> default). Also, if you set `gnutls-verify-error' to t, do you get the
> corresponding error in the non-NSM flow? "$HOSTNAME certificate could
> not be verified."
Yes:
Debugger entered--Lisp error: (error "Certificate validation failed 33.media.tumblr.com, verification code 2")
gnutls-boot(#<process nntpd<4>> gnutls-x509pki (:priority "NORMAL" :hostname "33.media.tumblr.com" :loglevel 0 :min-prime-bits 256 :trustfiles ("/etc/ssl/certs/ca-certificates.crt") :crlfiles nil :keylist nil :verify-flags nil :verify-error t :callbacks nil))
So I think the certificate just couldn't be verified, so this bug report
is, like, totally bogus, man.
Closing.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2014-12-08 20:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 18:01 bug#19098: 24.4.51; gnutls.c doesn't handle wildcard certificates Lars Magne Ingebrigtsen
2014-11-19 21:03 ` Ted Zlatanov
2014-12-08 20:11 ` Lars Magne Ingebrigtsen [this message]
2014-12-10 16:08 ` Ted Zlatanov
2014-12-10 16:27 ` Lars Magne Ingebrigtsen
2014-12-10 16:34 ` Ted Zlatanov
2014-12-21 12:10 ` Lars Ingebrigtsen
2014-12-24 12:49 ` Ted Zlatanov
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=m361dlsxyy.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=19098@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.