Hi frns,

I have the following tcpwrapper rule
#vi /etc/hosts.deny

sshd : ALL EXCEPT 192.168.0.100 : spawn /bin/echo `/bin/date` from %h >> /var/log/ssh.log : spawn (echo -e "Access denied to external ssh connection from %h " | mail -s "SSH connection denied" root@localhost) : DENY


I want the equivalent rule in iptables to log and send mail.

You want to deny ssh action to everyone except 192.168.0.100, refused attempts get logged (which must a big log file make.)

Presumably you can figure out how to rig policy deny, and accept incoming ssh connections by IP?

This leaves adding a log entry... which is just the same as the accept incoming, except it jumps to a log instead.

I think it is important that you understand your firewall. It is also good discipline to describe what you hope to acheive in normal language instead of trying to duplicate the effect from another application.

Hi

Thanks for the wise advice but at least i should get a mail when some one tries to ssh me...Can i achieve this through iptables or is there any other method except tcp-wrappers,port sentry and tripwire?

Regards,
Prayag

Yes, I already said, you can set iptables to write a log entry whenever a packet gets denied.

Something[*] like this:
iptables -A INPUT -p tcp -m tcp --dport 22 -m recent --name ssh --set -j LOG --log-prefix "SSH Attempt:"

... should appear after the -j ACCEPT entry for ssh from that one allowed IP. Since you have a default drop policy <raised eyebrow> you don't need an explicit DROP rule here.
[*]I don't do this myself, but I modified a rule to log portscans.
http://www.newartisans.com/blog_file...h.iptables.php
... caveat: these guys don't seem to use default DROP policies. Sad sad sad... you will always forget something: -P DROP catches it.

To be clear about the other things: Port Sentry is deprecated and should not be used anymore. Use something like Snort or Prelude if you want IDS capabilities or else something "simple" like PSAD could do. tripwire is a filesystem integrity checker like Aide, Samhain, Osiris and such has nothing to do with checking ports. Wrt to SSH it would be good to harden your setup, read the sticky Failed SSH login attempts thread and implement one of the solutions. The idea to e-mail an alert on tripping a port is nice if your part of the 'net doesn't receive any port probing but it is not an efficient or scalable solution.

Hi frns,
Thanks for the valuable suggestions.What i want was that i should get the alert through mail when the hacker attacks or even tries to attack my Server.So again in brief tell me how to prevent server from being hacked and get alerts.

Regards,
Prayag