Go to file
2021-08-17 13:40:17 +02:00
assets initial commit 2021-08-17 13:40:17 +02:00
src initial commit 2021-08-17 13:40:17 +02:00
.gitignore initial commit 2021-08-17 13:40:17 +02:00
Cargo.lock initial commit 2021-08-17 13:40:17 +02:00
Cargo.toml initial commit 2021-08-17 13:40:17 +02:00
README.md initial commit 2021-08-17 13:40:17 +02:00

README

Zunft - Zauberei und nftables

Now using the new Rust 2021 edition :)

Useful commands

cargo +nightly build --release && sudo setcap cap_net_admin+ep ./target/release/zunft && cargo +nightly run --release
sudo iptables -t filter -A INPUT -j NFQUEUE --queue-num 0 --queue-bypass
sudo iptables -L INPUT --line-numbers
sudo iptables -D INPUT 1

Testing the filter

While you can run whatever you want, the test case I made is for you to serve the assets folder with something like python -m http.server 8000, and then try to have a lookg at the files. Normally you should be able to get both files, but once the firewall runs, trying to access /secretshould not work anymore.