While doing a sudo apt upgrade, the crowdsec upgrade showed the following differences:
Setting up python3-jinja2 (3.1.2-1+deb12u2) ...
Setting up libglib2.0-data (2.74.6-2+deb12u6) ...
Setting up vim-common (2:9.0.1378-2+deb12u2) ...
Setting up libfreetype6:amd64 (2.12.1+dfsg-5+deb12u4) ...
Setting up xz-utils (5.4.1-1) ...
Setting up crowdsec-firewall-bouncer-iptables (0.0.34) ...
Configuration file '/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** crowdsec-firewall-bouncer.yaml (Y/I/N/O/D/Z) [default=N] ? D
--- /etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml 2025-02-15 10:02:50.297465972 +0000
+++ /etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.dpkg-new 2025-08-04 10:08:59.000000000 +0000
@@ -8,7 +8,7 @@
log_max_backups: 3
log_max_age: 30
api_url: http://127.0.0.1:8080/
-api_key: DNLn9mN1MNUzk4FujJscpZ1udBfLrcUjbjOmuemUJ74
+api_key: ${API_KEY}
## TLS Authentication
# cert_path: /etc/crowdsec/tls/cert.pem
# key_path: /etc/crowdsec/tls/key.pem
@@ -31,6 +31,7 @@
- INPUT
# - FORWARD
# - DOCKER-USER
+iptables_add_rule_comments: true
## nftables
nftables:
Configuration file '/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** crowdsec-firewall-bouncer.yaml (Y/I/N/O/D/Z) [default=N] ?
Progress: [ 76%] [#######################################################################.......................]
Given line 24 and 38, I figured the best course of action was to allow the update and figure out how to repair the api_key