Binary files /tmp/tmpw_d4qlvz/T5rYuHlkuj/iplock-3.0.55.1~lunar/debian/.changelog.swp and /tmp/tmpw_d4qlvz/o7FY9lHx6A/iplock-3.0.56.0~lunar/debian/.changelog.swp differ
diff -Nru iplock-3.0.55.1~lunar/debian/changelog iplock-3.0.56.0~lunar/debian/changelog
--- iplock-3.0.55.1~lunar/debian/changelog	2023-12-22 05:48:35.000000000 +0000
+++ iplock-3.0.56.0~lunar/debian/changelog	2024-01-06 22:21:44.000000000 +0000
@@ -1,4 +1,10 @@
-iplock (3.0.55.1~lunar) lunar; urgency=high
+iplock (3.0.56.0~lunar) lunar; urgency=high
+
+  * Changed the restart of rsyslogd using systemd.
+
+ -- Alexis Wilke <alexis@m2osw.com>  Sat, 06 Jan 2024 14:21:44 -0800
+
+iplock (3.0.55.1~bionic) bionic; urgency=high
 
   * Bumped build version to rebuild on Launchpad.
 
diff -Nru iplock-3.0.55.1~lunar/debian/iplock.postinst iplock-3.0.56.0~lunar/debian/iplock.postinst
--- iplock-3.0.55.1~lunar/debian/iplock.postinst	2023-12-05 05:15:00.000000000 +0000
+++ iplock-3.0.56.0~lunar/debian/iplock.postinst	2024-01-06 22:19:29.000000000 +0000
@@ -33,7 +33,11 @@
     if getent passwd syslog > /dev/null && getent group adm > /dev/null
     then
         chown syslog:adm /var/log/iptables
-        invoke-rc.d rsyslog restart
+
+        # TODO: test without this restart;
+        #       it looks like rsyslog now has a working trigger
+        #
+        systemctl restart rsyslog
     fi
 
     db_get ${PROJECTNAME}/public_interfaces
diff -Nru iplock-3.0.55.1~lunar/debian/iplock.postrm iplock-3.0.56.0~lunar/debian/iplock.postrm
--- iplock-3.0.55.1~lunar/debian/iplock.postrm	2022-11-06 00:39:19.000000000 +0000
+++ iplock-3.0.56.0~lunar/debian/iplock.postrm	2024-01-06 22:18:11.000000000 +0000
@@ -47,7 +47,7 @@
 
     # `01-iptables.conf` is now gone
     #
-    invoke-rc.d rsyslog restart
+    systemctl restart rsyslog
     rm -rf /var/log/iptables
 fi
 
diff -Nru iplock-3.0.55.1~lunar/debian/iplock.templates iplock-3.0.56.0~lunar/debian/iplock.templates
--- iplock-3.0.55.1~lunar/debian/iplock.templates	2023-12-06 04:45:43.000000000 +0000
+++ iplock-3.0.56.0~lunar/debian/iplock.templates	2023-12-30 14:21:52.000000000 +0000
@@ -16,16 +16,23 @@
 Type: string
 Description: Administrator IP Addresses
  Enter a comma separated list of IP addresses that the administrators use to
- access the system. Only use static IP addresses. If some of your
- administrators do not have a static IP address, you may want to look at using
- the knock-knock mechanism for SSH. This parameter can be left empty, however,
- if you are currently using SSH, you will get blocked by your new firewall.
+ access the system. Only use static IP addresses.
+ .
+ If some of your administrators do not have a static IP address, enter the
+ default IP address instead: 0.0.0.0/0. In this case, you may want to look
+ at using the knock-knock mechanism to connect to SSH. This makes it a
+ lot harder for a hacker to gain access even if they were able to determine
+ your private key.
+ .
+ On a console accessible computer, this parameter can be left empty, however,
+ if you are currently using SSH, you will get blocked by your new firewall
+ and the installation will freeze midway.
 
 Template: iplock/admin_interfaces
 Type: string
 Description: Administrator Interfaces
  Enter a comma separated list of interface names that the administrator(s) may
- use trying to connect to the server. This is used to only open the SSH serivce
+ use trying to connect to the server. This is used to only open the SSH service
  on those interfaces.
  .
  Note: this is likely the same as the public_interfaces parameter, although