Whilst the workaround above (just turning OFF encryption) will of course work, this bug is *still* present in libtorrent11_0.12.6-2. I'm actually wondering if it might be more an OpenSSL bug, or if not it's libtorrent's use of that. NB: I'm actually testing this specific libtorrent version as a backport into a Debian/lenny system as that's what my up 24/7 server runs and is where I run rtorrent. So that'd be openssl 0.9.8g-15+lenny7 in use. I also backported rtorrent 0.8.6-1 for use with this. I only did this after initially hitting the problem with lenny's versions.
For now I'm trying a libtorrent with the offending test and 'throw' commented out to see if it does any harm. I'm not familiar enough with the code to see exactly what the check is trying to prevent. -- - Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/ Finger athan(at)fysh.org for PGP key "And it's me who is my enemy. Me who beats me up. Me who makes the monsters. Me who strips my confidence." Paula Cole - ME -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
