Marc Haber said at 06/06/2007 15:44: > > I apologize for taking so much time to react. Thank you very much for > taking so much time to reproduce this issue.
Hi Marc.
No worries, it's the least I can do.
> On Sun, May 13, 2007 at 06:34:20PM +0100, Ronny Adsetts wrote:
>> Core was generated by `/usr/sbin/exim4 -bd -q30m -oX 587:465:25 -oP
>> /var/run/ex.
>> Program terminated with signal 11, Segmentation fault.
>>
>> [...]
>>
>> #0 _gnutls_read_uint16 (data=0x0) at gnutls_num.c:120
>> 120 gnutls_num.c: No such file or directory.
>> in gnutls_num.c
>> (gdb) bt
>> #0 _gnutls_read_uint16 (data=0x0) at gnutls_num.c:120
>> #1 0x00002ba3e841bfc9 in _gnutls_proc_rsa_client_kx (session=0x629e10,
>> data=0x0, _data_size=61) at auth_rsa.c:213
>> #2 0x00002ba3e84171e9 in _gnutls_recv_client_kx_message (session=0x629e10)
>> at gnutls_kx.c:333
>
> This looks like a GnuTLS issue to me.
Yeah, me too.
>> Please let me know if you want any more information.
>
> ldd /usr/sbin/exim4 | grep gnutls, and if possible, the exact Debian
> version of the libgnutls package which contains the library your exim4
> binbary is linked to.
$ ldd /usr/sbin/exim4 | grep gnutls
libgnutls.so.11 => /usr/lib/libgnutls.so.11 (0x0000002a96b96000)
$ dpkg-query -W 'libgnutls11'
libgnutls11 1.0.16-13.2sarge2
> I'll then clone and reassign the bug to the appropriate gnutls package.
Thanks.
From what I discovered when googling around, the problem *may* be limited to
amd64.
Ronny
--
Ronny Adsetts
Technical Director
Amazing Internet Ltd, London
t: +44 20 8607 9535
f: +44 20 8607 9536
w: www.amazinginternet.com
Registered office: UK House, 82 Heath Road, Twickenham TW1 4BW
Registered in England. Company No. 4042957
signature.asc
Description: OpenPGP digital signature
