Displaying 3 results from an estimated 3 matches for "fwcore_port_knock".
2024 Jul 04
1
Request for a Lockdown option
...P for 30 seconds.
836 0% 1 0% /root/port-knock-server PORT-NUMBER /root/bin/port-knock-client.sh
But it "integrates" into and relies upon the firewall via
# port_knock: input only server
if [ -n "${SERVER}" ] && fwcore_has_i port_knock; then
: ${FWCORE_PORT_KNOCK:?port_knock in FWCORE_IPROTOS needs FWCORE_PORT_KNOCK}
if ipaddr_split ap "${FWCORE_PORT_KNOCK}"; then
add_rule -p udp --dport ${port} \
-m recent --name port_knock --set \
-m recent --name port_knock...
2024 Jul 14
2
Request for a Lockdown option
P.S.:
Steffen Nurpmeso wrote in
<20240707025234.j3oUaPFH at steffen%sdaoden.eu>:
|Steffen Nurpmeso wrote in
| <20240704180538.iV4uex29 at steffen%sdaoden.eu>:
||Simon Josefsson wrote in
|| <87jzi1fg24.fsf at kaka.sjd.se>:
|||Jochen Bern <Jochen.Bern at binect.de> writes:
|||> (And since you mention "port knocking", I'd like to repeat how fond I
2024 Jul 04
4
Request for a Lockdown option
Jochen Bern <Jochen.Bern at binect.de> writes:
> (And since you mention "port knocking", I'd like to repeat how fond I
> am of upgrading that original concept to a single-packet
> crypto-armored implementation like fwknop.)
I am reluctantly considering to use some kind of port knocking mechanism
on some machines, however I really don't want to carry around shared