I should also add that another bug was filed downstream, reporting a
segfault in the event that the password contains a '# character.
Curiously, it doesn't seem to happen to everyone; for instance, David
Shen did not allude to a segfault (merely an authentication failure).
Here's a backtrace, courtesy of Joel Koglin:
gdb backtrace:
Thread 1 (Thread 0xb73758f0 (LWP 14276)):
#0 0x0804bd62 in ssmtp (argv=0x804f1e0) at ssmtp.c:1536
buf = '\000' <repeats 2048 times>
p = <value optimized out>
q = <value optimized out>
pw = 0xb7729c20
sock = 5
uid = 0
minus_v_save = <value optimized out>
timeout = <value optimized out>
#1 0x0804c4ff in main (argc=2, argv=0xbfd5d924) at ssmtp.c:2070
new_argv = 0x0
Original report here: http://bugs.gentoo.org/show_bug.cgi?id=313017
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
