From: boger <boger@ttk.ru>
To: gentoo-security@lists.gentoo.org
Subject: [gentoo-security] port knocking
Date: Tue, 11 Oct 2005 22:00:20 +0400 [thread overview]
Message-ID: <1699876524.20051011220020@ttk.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 449 bytes --]
This is result of last week discussion about port knockers.
Its my second bash script (first is my firewall), so any feedback will be appreshiated ;)
usage: ./knocker.sh <config file name> del
Path to config file is constant in knocker.sh.
del - is optional, simply deletes target chain
script has no limits on knock sequences, and demands statefull filtering enabled
ipt -i $IF_INET -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
[-- Attachment #2: knocker.sh --]
[-- Type: APPLICATION/OCTET-STREAM, Size: 2182 bytes --]
#!/bin/bash
IPTABLES="/sbin/iptables"
CONFIG_DIR="/root/knock/"
CHAIN_NAME=$1
CONFIG_FILE="${CONFIG_DIR}$1"
#overrideable in config file
IFACE='eth0'
CURRENT_PORT=1
ENDING_PORT=65534
TARGET_PORT=22
TIME=60
ABUSE_PERIOD=180
ABUSE_HITCOUNT=20
# file exists
if [[ ! -f ${CONFIG_FILE} ]]; then
echo " $CONFIG_FILE does not exist"
exit 1
fi
# syntax
if ! source ${CONFIG_FILE} ; then
echo "$CONFIG_FILE failed a sanity check"
exit 1
fi
# Helper function very usefull for debug
ipt(){
if !($IPTABLES "$@"); then
echo "$IPTABLES $@" ;
echo "abnormal termination"
exit 1
fi;
# debug
if [[ $DEBUG == "ON" ]]; then
echo $@
fi;
}
# found in emerge.sh not tested
sort() {
LC_ALL=C /bin/sort "$@"
}
#first, delete (possibly) existing rules
$IPTABLES -i $IFACE -D INPUT -p tcp --syn -j $CHAIN_NAME 2>/dev/null
$IPTABLES -F $CHAIN_NAME 2>/dev/null
$IPTABLES -X $CHAIN_NAME 2>/dev/null
#check if not just delete
if [[ $2 == "del" ]]; then
echo "$CHAIN_NAME deleted"
exit 0
fi
#create new chain
ipt -N $CHAIN_NAME
#first, send all incoming traffic to this chain
ipt -i $IFACE -I INPUT 1 -p tcp --syn -j $CHAIN_NAME
#########################################################
# fill chain #
#########################################################
#NAMES=""
for a in $PORTS; do
NAME="$CHAIN_NAME$a"
PORT=$((a - 1))
ipt -A $CHAIN_NAME -p tcp --syn --dport $CURRENT_PORT:$PORT -m recent --set --name ABUSE
# ipt -A $CHAIN_NAME -p tcp --syn --dport $a -m recent --remove --name $a
ipt -A $CHAIN_NAME -p tcp --syn --dport $a -m recent --set --name $NAME
# NAMES="$NAMES --name $a"
CURRENT_PORT=$((a + 1))
done;
#check last range
ipt -A $CHAIN_NAME -p tcp --dport $CURRENT_PORT:$ENDING_PORT -m recent --set --name ABUSE
# check for abusers
ipt -A $CHAIN_NAME -p tcp --dport $TARGET_PORT -m recent --rcheck --seconds $ABUSE_PERIOD --hitcount $ABUSE_HITCOUNT --name ABUSE -j RETURN
# check all names presents
for a in $PORTS; do
NAME="$CHAIN_NAME$a"
ipt -A $CHAIN_NAME -p tcp --dport $TARGET_PORT -m recent ! --rcheck --seconds $TIME --name $NAME -j RETURN
done;
# finaly allow target port
ipt -A $CHAIN_NAME -p tcp --dport $TARGET_PORT -j ACCEPT
[-- Attachment #3: test --]
[-- Type: APPLICATION/OCTET-STREAM, Size: 77 bytes --]
#!/bin/bash
PORTS="1000 2000 3000"
TARGET_PORT="22"
TIME="240"
DEBUG="ON"
next reply other threads:[~2005-10-11 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 18:00 boger [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-20 19:42 [gentoo-security] port knocking Jeff Gercken
2005-10-02 21:10 [gentoo-security] [OT?] automatically firewalling off IPs Jeremy Brake
2005-10-02 21:19 ` MaxieZ
2005-10-03 13:01 ` David vasil
2005-10-03 13:18 ` rpfc
2005-10-03 17:06 ` Kirk Hoganson
2005-10-04 16:25 ` boger
2005-10-04 17:16 ` Kirk Hoganson
2005-10-04 19:45 ` [gentoo-security] Port knocking Tobias Sager
2005-10-04 20:20 ` boger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1699876524.20051011220020@ttk.ru \
--to=boger@ttk.ru \
--cc=gentoo-security@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox