well one thing you can do to protect yourself from packet sniffing is use sftp instead of ftp. that encrypts all network information, so even if they sniff it, they can t read it.
in order for someone to sniff your info, they have to e on the same network segment as you, so that probably means that if you were comprimised that way, then someone else on your network was comprimised first.
also, traceroute defaults to go only 30 hops. but that doesn t mean anything. it just means that there are more than 30 routers between here and france, or whereever this person is.
my concern here is that OSX should not be as vulnerable as this. either OSX has a major security flaw which should be addressed, or there is some other insecure box on your network from which someone launched their attack, or installed a sniffer. you might consult with your netadmin to see look for sneaky behavior across your gateway, or just take a look at the inetd logs on the rest of the machine on your subnet. if inetd logging is not turned on, then turn it on.
in order for someone to sniff your info, they have to e on the same network segment as you, so that probably means that if you were comprimised that way, then someone else on your network was comprimised first.
also, traceroute defaults to go only 30 hops. but that doesn t mean anything. it just means that there are more than 30 routers between here and france, or whereever this person is.
my concern here is that OSX should not be as vulnerable as this. either OSX has a major security flaw which should be addressed, or there is some other insecure box on your network from which someone launched their attack, or installed a sniffer. you might consult with your netadmin to see look for sneaky behavior across your gateway, or just take a look at the inetd logs on the rest of the machine on your subnet. if inetd logging is not turned on, then turn it on.