From Fedora Project Wiki

m (Correct header.)
m (add important)
(7 intermediate revisions by 4 users not shown)
Line 1: Line 1:
= denyhosts - SOP =
{{header|infra}}
{{shortcut|ISOP:DENYHOSTS}}


== Contact Information ==
{{admon/important|This is important|This SOP has moved to the fedora Infrastructure SOP git repo. Please see the current document at: [http://infrastructure.fedoraproject.org/infra/docs/denyhosts.txt DenyHost] For changes, questions or comments, please contact anyone in the Fedora Infrastructure team. }}
Owner: Fedora Infrastructure Team


Contact: #fedora-admin, sysadmin-main group
[[Category:Infrastructure SOPs]]
 
Location: Anywhere
 
Servers: All
 
Purpose: Denyhosts provides a protection against brute force attacks.
 
== Description ==
 
All of our servers now implement denyhosts to protect against brute force attacks.  Very few boxes should be in the 'allowed' list.  Especially internally.  Right now lockbox and noc1 are the only two that are explicitly allowed.
 
== Troubleshooting and Resolution ==
 
=== Connection issues ===
The most common issue will be legitimate logins failing.  First, try to figure out why a host ended up on the deny list (tcptraceroute, failed login attempts, etc are all good candidates).  Next do the following directions.  The below example is for a host (10.0.0.1) being banned.  Login to the box from a different host and as root do the following.
 
<pre>
cd /var/lib/denyhosts
sed -si '/10.0.0.1/d' * /etc/hosts.deny
/etc/init.d/denyhosts restart
</pre>
 
That should correct the problem.

Revision as of 20:50, 29 March 2015

Shortcut:
ISOP:DENYHOSTS
Important.png
This is important
This SOP has moved to the fedora Infrastructure SOP git repo. Please see the current document at: DenyHost For changes, questions or comments, please contact anyone in the Fedora Infrastructure team.
Retrieved from "https://fedoraproject.org/w/index.php?title=Denyhosts_Infrastructure_SOP&oldid=408554"