NullNet-ai / NullNet-ai/nullnet
Derive the correct eBPF firewall ports allow-list based on the deployment environment
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5
- Forks
- 2
- Avg merge
- 3h 52m
- Merged PRs (30d)
- 19
Description
The eBPF firewall is default deny.
We should find a way to have the correct set of ports allowed based on the deployment environment.
Examples of needed open ports include SSH, Docker Swarm, DNS, DHCP, NTP.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the eBPF firewall implementation and the deployment-environment configuration in the repository. Review how the default-deny policy is assembled and identify the environments and required ports that must be represented. Done means the firewall derives the appropriate allow-list for each supported deployment environment, including the examples listed in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, rust
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100