Harden sysctl.conf by Sparrow checks
Harden sysctl.conf by Sparrow checks
Rules, and a bit of … Raku note: Harden sysctl.conf note: Rules taken from note: note: Controls the use of TCP syncookies note: Turn on SYN-flood protections note: regexp: ^^ “net.ipv4.…
You're viewing a single thread.
You definitely shouldn't copy and paste things like this.
sorry, could you please elaborate on "shouldn’t copy" ? thanks
For example if you blindly apply this and forget, you may encounter problems with ipv6 or with your vpn. So it's really depends on your use case and not hardening in general.
fair enough, however the intention is to show how one could create rules on Sparrow/Raku, not to show rules ... Maybe I should have mentioned that ...
for example this is more interesting example evaluation of net.ipv4.tcp_synack_retries"
regexp: ^^ "net.ipv4.tcp_synack_retries" \s* "=" \s* (\d+) \s* $$ generator: <<RAKU !raku if matched().elems { my $v = capture()[]; say "note: net.ipv4.tcp_synack_retries={$v}"; if $v >= 3 && $v <= 5 { say "assert: 1 net.ipv4.tcp_synack_retries in [3..5] range" } else { say "assert: 0 net.ipv4.tcp_synack_retries in [3..5] range" } } else { say "note: net.ipv4.tcp_synack_retries setting not found" } RAKU
you are seemed to have edited your initial reply - "it should be sysctl.conf not syslog.conf " - anyway thanks for that, now it's fixed, this was just overlook typo