Aras 'Russ' Memisyazici wrote: > GOAL: set-up a monitoring station that connects to all my *Nix boxes > every 15 minutes via an ssh attempt, if successful, log as such and move > on, if failure report so IMMEDIATELY! > > SETUP: several *Nix boxes with scrambled ssh ports all guided by > DenyHosts and iptables > > STEPS TAKEN: > > a) entered monitoring station's IP into usr/share/denyhosts/allowed-hosts
Wrong... it is /usr/share/denyhosts/data/allowed-hosts, not the one you used. > b) entered hostname of monitoring station into > usr/share/denyhosts/allowed-hosts > c) stopped/started DenyHosts > > RESULT1: > > getting email alert from DenyHosts that monitoring station was added to > deny list... Find out what was the reason the monitoring station was added. Improve your procedure: use public key, it never fails to log in. > d) log back on to blocked box and stop, remove IP from /host.deny, > re-start DenyHosts Wrong... that's not the procedure to clean up the mess. Read the recent post by Phil Schwartz with subject "Re: [Denyhosts-user] allowed-hosts problem (yes, another one!)", it points out a new option. -- René Berber ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Denyhosts-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/denyhosts-user
