all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 16253@debbugs.gnu.org
Subject: bug#16253: 24.3.50; Irrelevant warnings from gnutls
Date: Mon, 20 Jan 2014 11:11:29 -0500	[thread overview]
Message-ID: <87mwiqpr9q.fsf@flea.lifelogs.com> (raw)
In-Reply-To: <87eh45i2q2.fsf@building.gnus.org> (Lars Ingebrigtsen's message of "Sat, 18 Jan 2014 10:06:45 -0800")

On Sat, 18 Jan 2014 10:06:45 -0800 Lars Ingebrigtsen <larsi@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





  reply	other threads:[~2014-01-20 16:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-25  9:09 bug#16253: 24.3.50; Irrelevant warnings from gnutls Lars Ingebrigtsen
2014-01-07 23:47 ` Ted Zlatanov
2014-01-18 17:29   ` Lars Ingebrigtsen
2014-01-18 17:57     ` Eli Zaretskii
2014-01-20 16:11       ` Ted Zlatanov
2014-01-18 18:06     ` Lars Ingebrigtsen
2014-01-20 16:11       ` Ted Zlatanov [this message]
2014-01-20 20:19         ` Lars Ingebrigtsen
2014-02-10  2:34           ` Ted Zlatanov
2014-02-10  3:01             ` Lars Ingebrigtsen
2014-02-10 10:42               ` Ted Zlatanov
2014-12-08 19:58 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mwiqpr9q.fsf@flea.lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=16253@debbugs.gnu.org \
    --cc=larsi@gnus.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.