I want to create a postoverflow whitelist, so my dynamic IP address from my ISP won't get blocked, when I access and test configurations on my cloud machines.
DynDNS is configured.
I already installed the postverflow rdns parser : https://app.crowdsec.net/hub/author/crowdsecurity/postoverflows/rdns
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
POSTOVERFLOWS
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Name π¦ Status Version Local Path
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
crowdsecurity/rdns βοΈ enabled 0.3 /etc/crowdsec/postoverflows/s00-enrich/rdns.yaml
I was looking at the examples from the documentation: https://docs.crowdsec.net/docs/v1.4.0/whitelist/create
It says to put the whitelist yaml file in
/etc/crowdsec/postoverflows/s01-whitelist/
But when I was looking for that folder I only found
/etc/crowdsec/postoverflows/s00-enrich
where the rdns.yaml is available.
Is this by any chance an outdated instruction and not applicable to a newer version of crowdsec and do I have to create that folder myself manually?
But there is also a whitelist.yaml inside:
/etc/crowdsec/hub/parsers/s02-enrich/crowdsecurity/whitelists.yaml
But I guess this is the Parser Whitelist and not the Postoverflow whitelist as mentioned in the documentation.