fwknop
homecontroller
| fwknop | homecontroller | |
|---|---|---|
| 10 | 2 | |
| 1,028 | 4 | |
| - | - | |
| 7.3 | 8.7 | |
| about 1 month ago | 12 days ago | |
| Perl | Shell | |
| GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fwknop
-
Fail2ban Sucks
sounds fun; i see the arch aur has a few options as well. have you tried https://www.cipherdyne.org/fwknop/ ?
-
Has anyone ever had their homelab or network hacked? What happened?
Yes that's the basic idea, i tried to use fwknop first but it didn't do what i wanted it to do so i made my own
-
How to securely enable SSH access to my home network?
Port knocking. Or better yet FWKNOP. I'm disappointed I don't hear people talk about it more. The port isn't even open until you give the secret combination of knocks on a large number of ports. There's much more to it. I recommend listening to Episode 865 ofSecurity Now.
-
Show HN: Knockles – eBPF Port Knocking Tool
> Is this approach used elsewhere?
Yes, or at least in a similar fashion. An alternative variant of port knocking is SPA (Single Packet Authorization). Often SPA protocols use UDP and contain within the body field an encrypted payload containing all the required data to authenticate and authorize a particular request.
There are multiple different implementations of SPA: OpenSPA [1] (full disclosure: I am the author of OpenSPA), fwknop [2] just to name a few.
SDP (Software Defined Perimeter) often builds upon SPA technologies in order to achieve a form of zero trust access.
[1] - https://github.com/greenstatic/openspa
[2] - https://github.com/mrash/fwknop
I am currently re-writting the OpenSPA protocol (version 2) and I plan on playing around with eBPF as well, so thanks eeriedusk for paving the way :)
-
Blocking SSH Bot Net Attack
As an alternative to port knocking, there is: https://github.com/mrash/fwknop
-
Start VPN server based on external trigger
fwknop is nice and simple
-
UFW setup for decent security
Sure, few links for when you dig in: http://iplists.firehol.org/, https://crowdsec.net/, https://www.zeroflux.org/projects/knock/, https://www.cipherdyne.org/fwknop/
-
Who's Attacking My Server?
An upgrade to port knocking is Single Packet Authorization [1]. It doesn’t suffer from the observability, and other, problems of port knocking.
[1] https://www.cipherdyne.org/fwknop/
-
How Self Hosting (and password reuse) led to the compromise of Linked In, Dropbox, & more.
Or keep the port closed like I do with my ssh port and use fwknop to open the port only when needed.
homecontroller
-
Point to non-docker services via traefik
You can find more details in the Traefik File documentation. I've shared my personal configuration on my GitHub if you like an example.
-
UFW setup for decent security
Sounds a lot like the way I’ve setup my personal environment. I’ve documented it on GitHub, including how I’ve restricted ssh (cert only) and configured ufw
What are some alternatives?
pfSense - Main repository for pfSense
knock - A port-knocking daemon
Fail2Ban - Daemon to ban hosts that cause multiple authentication errors
crowdsec - CrowdSec - the open-source and participative security solution offering crowdsourced protection against malicious IPs and access to the most advanced real-world CTI.
OSQuery - SQL powered operating system instrumentation, monitoring, and analytics.
autoVPN - Create On Demand Disposable OpenVPN Endpoints on AWS.
Glastopf - Web Application Honeypot
trasa - Zero Trust Service Access
Wazuh - Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
Blackbox - Safely store secrets in Git/Mercurial/Subversion
Snort - Snort++