Dec 17, 2016 05:38 AM
(This post was last modified: Dec 17, 2016 02:52 PM by slober.)
Make your system - RASPBERRY PI - a bit more secure!
IoT is awesome!
Code
FailIP.txt
AttemptsFailedPasswords. IP
1 109.226.102.146
1 111.243.15.91
1 111.249.213.229
361 112.132.231.1
3634 116.31.116.23
44926 116.31.116.28
1 14.161.76.196
1 14.162.122.119
1 14.162.185.114
1 14.169.136.214
1 14.184.39.191
1 14.186.205.101
1 14.186.27.1
12 142.54.173.251
989 153.99.182.2
1 176.51.134.101
1 176.51.64.33
1 178.123.206.23
1 178.65.64.34
6 179.40.164.41
294 182.100.67.120
1 182.74.203.78
6 185.110.132.202
1 188.17.152.177
6 191.82.60.217
4 192.162.101.217
4 194.63.141.141
1 195.168.172.14
1 195.20.3.210
1 195.77.36.85
1 201.71.141.79
8 212.83.128.148
1 213.228.79.39
360 218.65.30.134
223 218.65.30.43
1 36.228.79.35
1 36.239.147.49
1 37.252.92.220
1 37.252.94.26
1 37.252.94.89
1 37.252.95.86
4 38.84.132.236
1 41.237.108.112
6 45.21.91.114
12 51.254.116.228
5 5.196.76.41
9205 59.63.166.83
1 81.90.227.12
1 90.232.44.4
47 91.224.160.108
47 91.224.161.88
1 91.44.158.238
186 92.63.249.14
1 93.183.253.205Due to the increasing number of connected devices the number of Bots and crawlers are also increasing.
which can and will! result in your server being attacked sooner or later.
Code
44926 116.31.116.2844 926 Failed login Attempts from this guy!
Let's fix this!
First of all you should check if you are being attacked or something like that
you could do this with this script:
If it looks nasty you should keep reading. ✌
We'll use the tool Fail2Ban to secure our system
www.fail2ban.org Wrote:Fail2ban scans log files (e.g. /var/log/apache/error_log) and bans IPs that show the malicious signs -- too many password failures, seeking for exploits, etc. Generally Fail2Ban is then used to update firewall rules to reject the IP addresses for a specified amount of time, although any arbitrary other action (e.g. sending an email) could also be configured. Out of the box Fail2Ban comes with filters for various services (apache, courier, ssh, etc).
Fail2Ban is able to reduce the rate of incorrect authentications attempts however it cannot eliminate the risk that weak authentication presents. Configure services to use only two factor or public/private authentication mechanisms if you really want to protect services.
Code
sudo apt-get install fail2banAfter this you're pretty much done but there are some extras you could do.
goto /etc/fail2ban/jail.conf
Code
sudo nano /etc/fail2ban/jail.conf
OR
sudo vi /etc/fail2ban/jail.conffind the line [ssh] or another service [YOUR_SERVICE] you wish to change.
Code
banaction = iptables-allports
bantime = 3600
maxretry = 3After this you just need to restart the server:
Code
sudo service fail2ban restartSome usefull commands
Code
# View all banned ip's
sudo iptables -L -n
# Reset iptables
sudo iptables -FNow we're at least a little bit safer!
Code
target prot opt source destination
REJECT all -- 218.65.30.134 0.0.0.0/0 reject-with icmp-port-unreachable
REJECT all -- 182.100.67.120 0.0.0.0/0 reject-with icmp-port-unreachable
REJECT all -- 115.239.248.35 0.0.0.0/0 reject-with icmp-port-unreachable
REJECT all -- 106.247.230.226 0.0.0.0/0 reject-with icmp-port-unreachable
REJECT all -- 116.31.116.48 0.0.0.0/0 reject-with icmp-port-unreachable
REJECT all -- 185.110.132.202 0.0.0.0/0 reject-with icmp-port-unreachable
REJECT all -- 51.254.116.228 0.0.0.0/0 reject-with icmp-port-unreachable
REJECT all -- 116.31.116.23 0.0.0.0/0 reject-with icmp-port-unreachable
RETURN all -- 0.0.0.0/0 0.0.0.0/0
Public Honeypot Project: https://github.com/Slober3/PotHead
Honeypot Twitter: https://twitter.com/HoneyHive9
BTC: 1Anime1QrjwsEmz8bC2FwVcNXDLxP3SWAJ
Honeypot Twitter: https://twitter.com/HoneyHive9
BTC: 1Anime1QrjwsEmz8bC2FwVcNXDLxP3SWAJ
Erin Wrote:It’s fine. There’s nothing to be afraid of. Calm down, Lilan



![[Image: winged_scarab_white.png]](https://imageupload.co.uk/images/2016/11/05/winged_scarab_white.png)