• melezhikOP
      link
      fedilink
      arrow-up
      2
      ·
      5 hours ago

      sorry, could you please elaborate on “shouldn’t copy” ? thanks

      • nesc@lemmy.cafe
        link
        fedilink
        English
        arrow-up
        3
        ·
        5 hours ago

        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.

        • melezhikOP
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          5 hours ago

          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
          
    • melezhikOP
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      5 hours ago

      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