GNU bug report logs - #16253
24.3.50; Irrelevant warnings from gnutls

Previous Next

Package: emacs;

Reported by: Lars Ingebrigtsen <larsi <at> gnus.org>

Date: Wed, 25 Dec 2013 09:16:02 UTC

Severity: minor

Tags: fixed

Merged with 18148, 25396

Found in versions 24.3.50, 24.3.92, 24.5

Fixed in versions 25.1, 26.1

Done: Lars Magne Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #20 received at 16253 <at> debbugs.gnu.org (full text, mbox):

From: Ted Zlatanov <tzz <at> lifelogs.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 16253 <at> debbugs.gnu.org
Subject: Re: bug#16253: 24.3.50; Irrelevant warnings from gnutls
Date: Mon, 20 Jan 2014 11:11:29 -0500
On Sat, 18 Jan 2014 10:06:45 -0800 Lars Ingebrigtsen <larsi <at> gnus.org> wrote: 

LI> Speaking of irrelevant messages.  I just got this:
LI> gnutls.c: [0] (Emacs) fatal error: An unexpected TLS handshake packet was received.
LI> gnutls.el: (err=[-19] An unexpected TLS handshake packet was
LI> received.) boot: (:priority NORMAL :hostname i.chzbgr.com :loglevel 0
LI> :min-prime-bits 256 :trustfiles (/etc/pki/tls/certs/ca-bundle.crt)
LI> :crlfiles nil :keylist nil :verify-flags nil :verify-error nil
LI> :callbacks nil)

LI> Errors like this are to be expected (the server just closes the
LI> connection for some reason or other).  The URL library should deal with
LI> this without bothering the user with these warnings...

The URL library can't trap these.  GnuTLS considers them highest
priority, so blocking them out would block most useful log information.
I'm not sure what to do without breaking things or complicating the
configuration significantly.

Ted




This bug report was last modified 8 years and 190 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.