RE: strano bof nel traceroute...

Ciao
a proposito del bof mi sa che e' proprio il bfbtester che da' i numeri
infatti se fai:
root ~/targzip/bfbtester-2.0.1/src/bfbt:> ./bfbtester -s /bin/ping 
=> /bin/ping
 (setuid: 0)
   * Single argument testing
*** Crash </bin/ping> ***
args:           -n [51200]
envs:           
Signal:         11 ( Segmentation fault )
Core?           Yes

e poi vai a vedere il core:
root ~/targzip/bfbtester-2.0.1/src/bfbt:> gdb /bin/ping core
.............
Core was generated by `/bin/ping AAAAAAAAAAAAAAAA....'.
Program terminated with signal 11, Segmentation fault.
#0  0x40070015 in __overflow (f=0x40106d20, ch=-1) at genops.c:197
197     genops.c: No such file or directory.
(gdb) bt
#0  0x40070015 in __overflow (f=0x40106d20, ch=-1) at genops.c:197
#1  0x4006ef10 in _IO_new_file_xsputn (f=0x40106d20, data=0xbfff0960, n=8192) at fileops.c:803
#2  0x4006379c in _IO_helper_overflow (s=0xbfff08ac, c=65) at vfprintf.c:1704
#3  0x40070017 in __overflow (f=0xbfff08ac, ch=65) at genops.c:197
#4  0x400637bb in _IO_helper_overflow (s=0xbfff08ac, c=65) at vfprintf.c:1707
#5  0x40070017 in __overflow (f=0xbfff08ac, ch=65) at genops.c:197
#6  0x400637bb in _IO_helper_overflow (s=0xbfff08ac, c=65) at vfprintf.c:1707
#7  0x40070017 in __overflow (f=0xbfff08ac, ch=65) at genops.c:197
#8  0x400637bb in _IO_helper_overflow (s=0xbfff08ac, c=65) at vfprintf.c:1707
#9  0x40070017 in __overflow (f=0xbfff08ac, ch=65) at genops.c:197
#10 0x400637bb in _IO_helper_overflow (s=0xbfff08ac, c=65) at vfprintf.c:1707
......................
e cosi' di seguito non so per quanto....
mi sa che c'e' come dicevi tu che c'e' un sovrannumero di threads.

Stesso discorso con /bin/su...

Altra cosa e' capire come succede.

bye
Stefano.

________________________________________________________
http://www.sikurezza.org - Italian Security Mailing List