unofficial mirror of bug-gnu-emacs@gnu.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: Tue, 07 Jan 2014 18:47:12 -0500	[thread overview]
Message-ID: <87mwj7bbi7.fsf@flea.lifelogs.com> (raw)
In-Reply-To: <87vbydjnzy.fsf@building.gnus.org> (Lars Ingebrigtsen's message of "Wed, 25 Dec 2013 10:09:21 +0100")

On Wed, 25 Dec 2013 10:09:21 +0100 Lars Ingebrigtsen <larsi@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





  reply	other threads:[~2014-01-07 23:47 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 [this message]
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
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

  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=87mwj7bbi7.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 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).