Project status? #3
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi there,
I have no idea how, but your project never appeared in my searches for a similar thing. So much so I started https://github.com/andaru-project/andaru.
It seems our goals are similar: to provide an AGPLv3 Debian-based firewall that can be installed on top of Debian.
I'd like to know what's your roadmap like at the moment, how open you are to mostly AI-written contributions (mostly because I lack the free time to put effort beyond designing, spec'ing and QA), and so on.
No need to reinvent the wheel. It seems you got a good deal of progress on it already.
Hello @andrebrait,
i just saw that somehow my repo made it to the top of google, i did not expect that. I started like 4 Years ago and have been doing work when i find time. I haven't announced it anywhere because while it does work for me mostly, It does has some very sharp edges which need to be resolved before letting people play with it.
My current goal is more like a Appliance to reduce the attack Surface, prevent rootkits, contain infections and lower the chance of breakage. Based on Debian, Immutable, Signed UKI with custom Secureboot Cert, A/B Updates via systemd-sysupdate, locked down services with apparmor. But i would be open to talk about having a more open installable mode if that is what you want.
I can live with AI contributions as long as they are not massive changes, don't have unnecessary comments and you understand how the Code actually works and have reviewed it yourself.
If you are still interested then i can go through my pile of local changes and notes to write a public Roadmap.
@andrebrait i have taken some time to write a high level roadmap here speatzle/nfsense#4
Sorry for the delay, but Gmail thought your emails were span.
I will take a look. Regarding AI, yeah, balancing things out is tough. It can easily become "too much".
Other than the fact I wish I could have a more modern firewall OS, the thought of starting my own pfSense-like system came from the frustrations I found while working on pfBlockerNG alongside BBcan177. We moved a lot of things off Netgate's control and we have our own repository and everything now, plus plans to make it so that we can bring its functionality to essentially anything capable of running Go; but we're just now polishing some rough edges and preparing for an eventual v4.0.0 release.
I'll take a look at your stuff more in depth and all, but first I wanted to know if you even had intentions to move forward with it, so I'm glad to see you do.
No problem. Google does not care that my email Reputation is perfect, i don't send enough emails to them so they have limited data so everything goes to spam even if their own console tells you everything is fine.
I used pfBlockerNG before the Netgate opnsense website drama years ago, worked well. Since then i have started working in IT Security and have hands on Experience with Enterprise Firewalls Like Paloalto, Fortinet and Smaller ones like the Sophos UTM or XG. I started nfsense to make a better Firewall based on Linux using the things i thought where good from each of the Vendors (Commits like Palo, UI more like Forti and Address Objects like UTM).
The Readme instructions are outdated, but to get a usable image you can build the image with ./build_image.sh which mainly requires a recent version of mkosi. Then you can put the qcow2 in a Qemu VM and boot it, login and set a initial ip. You should now be able to access the webinterface on 4444 and configure the ip again so that nfsense will set it on apply.