Package: cryptcat Version: 20031202-2+b1 Severity: grave Justification: renders package unusable
In order to test sending files with cryptcat, I have run one instance like so: cryptcat -l -p 11223 > myfile.sent And then I start another instance on the same machine to send the file to the first instance: cat myfile | cryptcat 127.0.0.1 11223 Instantly the first instance of cryptcat crashes. I have run this under a debugger and it appears there is serious memory corruption occurring. Specifically, when a C++ method is run, it's own "this" variable appears to be corrupt. In any case, I don't have time to debug it now, but perhaps someone else knows of an easy fix. I get the same behavior on two separate machines, one a 32-bit AMD system, and another which is a 32 bit Intel-based Mac. Notably, this crash doesn't occur for me if I run the second cryptcat instance like: echo test | cryptcat 127.0.0.1 11223 This indicates to me that an overflow of some kind could be occurring. Be sure to test using large files to trigger it. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.20 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages cryptcat depends on: ii libc6 2.5-10 GNU C Library: Shared libraries ii libgcc1 1:4.2-20070528-1 GCC support library ii libstdc++6 4.2-20070528-1 The GNU Standard C++ Library v3 cryptcat recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
