Re: NPTd woes
Grishnav <[email protected]>
| Newsgroups | gmane.org.user-groups.linux.pdxlug |
|---|---|
| Message-ID | <[email protected]> |
Charlie Schluting wrote: > Grishnav wrote: > >> I don't get it. :-( >> >> egosurf root # lsof -i UDP:123 >> COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME >> ntpd 7154 ntp 4u IPv4 10402255 UDP *:ntp >> ntpd 7154 ntp 5u IPv4 10402256 UDP localhost:ntp >> ntpd 7154 ntp 6u IPv4 10402257 UDP egosurf.net:ntp >> egosurf root # iptables -L >> Chain INPUT (policy ACCEPT) >> target prot opt source destination >> ACCEPT tcp -- anywhere anywhere tcp dpt:ssh >> DROP tcp -- anywhere anywhere tcp >> dpt:5222 >> DROP tcp -- anywhere anywhere tcp >> dpt:imap2 >> DROP tcp -- anywhere anywhere tcp >> dpt:pop3 > > > Aren't you missing something here? > Or is it default to accept? (sorry.. I don't use iptables) > :) Accept is default... Chain INPUT (policy ACCEPT) Chain OUTPUT (policy ACCEPT) etc... The iptables rules are really only there as blunt encouragement to connect to the encrypted version of my services rather than the plaintext ones (which I mainted for a while because of lack of ssl support in the webmail software I was using at the time). The hole for ssh is because I occasionally accidently connect to a port that I've got portsentry monitoring and I need to keep from locking myself out.