GNU bug report logs -
#16253
24.3.50; Irrelevant warnings from gnutls
Previous Next
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
View this message in rfc822 format
On Wed, 25 Dec 2013 10:09:21 +0100 Lars Ingebrigtsen <larsi <at> gnus.org> wrote:
LI> When a TLS server shuts down the connection to Emacs (for instance, when
LI> timing out a https connection), Emacs gives this ominous warning:
LI> gnutls.c: [0] (Emacs) fatal error: The TLS connection was non-properly terminated.
LI> Normal network connections don't give any warnings, so TLS connections
LI> shouldn't, either.
I added this:
#ifdef HAVE_GNUTLS3
/* Function to log a simple audit message. */
static void
gnutls_audit_log_function (gnutls_session_t session, const char* string)
{
if (global_gnutls_log_level >= 1)
{
message ("gnutls.c: [audit] %s", string);
}
}
#endif
...
#ifdef HAVE_GNUTLS3
fn_gnutls_global_set_audit_log_function (gnutls_audit_log_function);
#endif
...so if this is an auditing message, you should see the "[audit]"
prefix. Since you don't, either you're on GnuTLS 2.x (unlikely) or
GnuTLS is saying it's a very high priority message that shouldn't be
filtered out. I could add special handling for this specific message
but is that the right thing to do?
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.