Control: severity -1 important
[Jakub Wilk]
> FWIW, I can't reproduce the bug on i386 with eatmydata_26-2 either.
Good. I'm raising the severity to important. It might even be argued
that this is release critical, but I will not raise it that high yet.
I suggest the 'eatmydata gnutls-cli jwilk.net' test case is added to
the test suite to make sure this bug do not make it into the archive
in the future. Did anyone talk to upstream about the problem?
I tried running 'gnutls-cli' on its own on i386, and this demonstrate
that no DNS name is needed to trigger the bug:
% eatmydata gnutls-cli
sh: 1: gcc: not found
dpkg-architecture: warning: couldn't determine gcc system type, falling back
to default (native compilation)
Error in GnuTLS initialization: Failed to acquire random data.
No hostname specified
% gnutls-cli
No hostname specified
%
After installing libgnutls28-dbg I tried running the program in gdb to
get a backtrace. This is what I get for breaking on write(), used to
print the error message:
(gdb) bt
#0 write () at ../sysdeps/unix/syscall-template.S:81
#1 0xb7d22791 in _IO_new_file_write (f=0xb7e5b960 <_IO_2_1_stderr_>,
data=0xbfffd030, n=63)
at fileops.c:1253
#2 0xb7d219ef in new_do_write (fp=fp@entry=0xb7e5b960 <_IO_2_1_stderr_>,
data=data@entry=0xbfffd030 "Error in GnuTLS initialization: Failed to
acquire random data.\n",
to_do=to_do@entry=63) at fileops.c:530
#3 0xb7d22e42 in _IO_new_file_xsputn (f=0xb7e5b960 <_IO_2_1_stderr_>,
data=0xbfffd030, n=63)
at fileops.c:1335
#4 0xb7cfbf3a in buffered_vfprintf (s=s@entry=0xb7e5b960 <_IO_2_1_stderr_>,
format=format@entry=0xb7f61484 "Error in GnuTLS initialization: %s\n",
args=args@entry=0xbffff5ac
"\374\376\365\267\062\377\377\377@\311\373\267\001") at vfprintf.c:2333
#5 0xb7cf7335 in _IO_vfprintf_internal (s=s@entry=0xb7e5b960
<_IO_2_1_stderr_>,
format=format@entry=0xb7f61484 "Error in GnuTLS initialization: %s\n",
ap=ap@entry=0xbffff5ac "\374\376\365\267\062\377\377\377@\311\373\267\001")
at vfprintf.c:1290
#6 0xb7dac5d8 in ___fprintf_chk (fp=0xb7e5b960 <_IO_2_1_stderr_>, flag=1,
format=0xb7f61484 "Error in GnuTLS initialization: %s\n") at
fprintf_chk.c:35
#7 0xb7e9c11d in fprintf (__fmt=0xb7f61484 "Error in GnuTLS initialization:
%s\n",
__stream=<optimized out>) at /usr/include/i386-linux-gnu/bits/stdio2.h:97
#8 lib_init () at gnutls_global.c:424
#9 0xb7fed86e in call_init (l=<optimized out>, argc=argc@entry=1,
argv=argv@entry=0xbffff654,
env=env@entry=0xbffff65c) at dl-init.c:78
#10 0xb7fed964 in call_init (env=0xbffff65c, argv=0xbffff654, argc=1,
l=<optimized out>) at dl-init.c:36
#11 _dl_init (main_map=0xb7fff930, argc=1, argv=0xbffff654, env=0xbffff65c) at
dl-init.c:126
#12 0xb7fdfd3f in _dl_start_user () from /lib/ld-linux.so.2
(gdb)
I also tried to break on open() to see if something tried to open
/dev/random or similar, but did not see any such call.
--
Happy hacking
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
