Sorry for not replying sooner, thanks for the ping. On Mon, 2008-02-04 at 16:31 +0100, Daniel Baumann wrote:
> First, I believe that the issue about 'tcptracroute report is more > verbose' is fixed since 2.0.9. At least, when tracerouting google here, > it's as verbose as the original tcptracreoute: Here, the original tcptraceroute is still better: [EMAIL PROTECTED]:~$ dpkg -s traceroute | grep Version Version: 2.0.11-1 [EMAIL PROTECTED]:~$ dpkg -s tcptraceroute | grep Version Version: 1.5beta6-2.1 [EMAIL PROTECTED]:~$ sudo tcptraceroute.mt google.com Selected device eth0, address 10.1.1.3, port 53477 for outgoing packets Tracing the path to google.com (64.233.187.99) on TCP port 80 (www), 30 hops max 1 10.1.1.1 0.290 ms 0.216 ms 0.209 ms 2 per9.ba.optusnet.com.au (198.142.131.10) 16.575 ms 16.699 ms 15.898 ms 3 per4-ge1-0-447.gw.optusnet.com.au (198.142.49.161) 16.454 ms 17.574 ms 16.234 ms 4 sun2-ge1-2-900.gw.optusnet.com.au (198.142.160.106) 64.218 ms 62.968 ms 62.899 ms 5 mas3-ge11-0-0-821.gw.optusnet.com.au (211.29.156.11) 78.260 ms 78.377 ms 78.683 ms 6 203.208.191.5 234.265 ms 234.028 ms 232.986 ms 7 ge-4-0-0-0.laxow-dr2.ix.singtel.com (203.208.149.34) 236.896 ms 235.817 ms 236.918 ms 8 203.208.169.50 236.914 ms 235.748 ms 236.429 ms 9 216.239.46.180 232.784 ms 233.114 ms 234.743 ms 10 216.239.43.125 289.962 ms 288.433 ms 287.409 ms 11 216.239.47.1 290.904 ms 291.449 ms 291.604 ms 12 216.239.49.222 298.702 ms 289.940 ms 289.876 ms 13 jc-in-f99.google.com (64.233.187.99) [open] 294.104 ms 293.497 ms 295.515 ms [EMAIL PROTECTED]:~$ sudo tcptraceroute.db google.com traceroute to google.com (64.233.167.99), 30 hops max, 40 byte packets 1 10.1.1.1 (10.1.1.1) 0.618 ms 0.659 ms * 2 * * * 3 * * * 4 * * * 5 * * * 6 * 203.208.192.97 (203.208.192.97) 234.820 ms 236.159 ms 7 * * * 8 * * * 9 * * * 10 * * * 11 * * 216.239.46.45 (216.239.46.45) 286.302 ms 12 64.233.174.81 (64.233.174.81) 285.708 ms * 216.239.46.45 (216.239.46.45) 291.466 ms 13 * * * 14 * * * 15 * * * 16 * * * 17 * * py-in-f99.google.com (64.233.167.99) 284.325 ms [EMAIL PROTECTED]:~$ sudo tcptraceroute.mt optusnet.com.au Selected device eth0, address 10.1.1.3, port 53609 for outgoing packets Tracing the path to optusnet.com.au (211.29.132.105) on TCP port 80 (www), 30 hops max 1 10.1.1.1 0.252 ms 0.195 ms 0.182 ms 2 per9.ba.optusnet.com.au (198.142.131.10) 17.153 ms 16.788 ms 18.247 ms 3 per4-ge1-0-447.gw.optusnet.com.au (198.142.49.161) 17.893 ms 17.839 ms 18.199 ms 4 sun2-ge1-2-900.gw.optusnet.com.au (198.142.160.106) 78.099 ms 79.583 ms 78.516 ms 5 mas2-ge14-0-0-821.gw.optusnet.com.au (211.29.156.10) 78.925 ms 79.536 ms 78.673 ms 6 mas5-unk8-1.gw.optusnet.com.au (211.29.129.142) 78.757 ms 78.562 ms 78.787 ms 7 www.optusnet.com.au (211.29.132.105) [open] 77.095 ms 77.126 ms 76.392 ms [EMAIL PROTECTED]:~$ sudo tcptraceroute.db optusnet.com.au traceroute to optusnet.com.au (211.29.132.105), 30 hops max, 40 byte packets 1 10.1.1.1 (10.1.1.1) 0.643 ms 0.640 ms * 2 * * * 3 * * * 4 * * * 5 * * * 6 * mas5-unk8-1.gw.optusnet.com.au (211.29.129.142) 79.076 ms 80.817 ms 7 www.optusnet.com.au (211.29.132.105) 80.282 ms 82.442 ms 84.642 ms > Second, traceroute running in tcptracroute-mode requires root > privileges, that's right. But so does original tcptraceroute (it's just > that the binary is suid-root in the package to achieve for that). Do you > think it is a good idea to make traceroute suid-root too? I'm not so > fond of that. Agreed. It would be nice if the original tcptraceroute was audited or had the setuid bit removed. -- bye, pabs http://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
