On Wed, Dec 04, 2013 at 04:07:42AM +0000, j...@jedsoft.org wrote: > On Tue, 3 Dec 2013 22:02:05 +0100, Moritz Muehlenhoff <j...@debian.org> said: > >src/sltcp.c in slrn 1.0.1 raised this to > > > >gnutls_global_set_log_level(4711); > > > >Was that intended or debugging leftover? > > That value has been there from pre1.0.0-18, when I added the call to > gnutls_global_set_log_level. I will push a change that uses a level > of 0, if that solves the problem. Could the real culprit be a > regression in gnutls?
At least in the 1.0.0~pre18 version previously in Debian the code isn't present, her's the diff to our 1.0.1 currently in sid: +#if SLTCP_HAS_GNUTLS_SUPPORT + gnutls_global_set_log_function(tls_log_func); + gnutls_global_set_log_level(4711); +#endif This might a general gnutls issue, but I know gnutls very well and I suppose most people outside of Debian use OpenSSL. I think setting it to 0 is the sane default anyway, it can be enabled in a local build if there're problems. Unrelated to the SSL bug there was also a bugreport complaining about too much logging: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729901 Thanks for the quick reponse; I'll cherrypick 107be9a749993d0063d4e87330ab947084d10c47 for an upcoming Debian upload. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
