[Bug 1823051] Re: knockd can't use ufw

2021-11-07 Thread Bug Watch Updater
** Changed in: knockd (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823051 Title: knockd can't use ufw To manage notifications about this bug go to: htt

[Bug 1823051] Re: knockd can't use ufw

2019-05-09 Thread Launchpad Bug Tracker
This bug was fixed in the package knockd - 0.7-1ubuntu1.18.04.2 --- knockd (0.7-1ubuntu1.18.04.2) bionic; urgency=medium * d/knockd.service: - Change ProtectSystem to 'true', to allow using ufw in knockd rules (LP: #1823051) - Add CAP_SYS_MODULE so knockd can load ipta

[Bug 1823051] Re: knockd can't use ufw

2019-05-09 Thread Launchpad Bug Tracker
This bug was fixed in the package knockd - 0.7-1ubuntu1.18.10.2 --- knockd (0.7-1ubuntu1.18.10.2) cosmic; urgency=medium * d/knockd.service: - Change ProtectSystem to 'true', to allow using ufw in knockd rules (LP: #1823051) - Add CAP_SYS_MODULE so knockd can load ipta

[Bug 1823051] Re: knockd can't use ufw

2019-05-09 Thread Launchpad Bug Tracker
This bug was fixed in the package knockd - 0.7-1ubuntu2.1 --- knockd (0.7-1ubuntu2.1) disco; urgency=medium * d/knockd.service: - Change ProtectSystem to 'true', to allow using ufw in knockd rules (LP: #1823051) - Add CAP_SYS_MODULE so knockd can load iptables modules

[Bug 1823051] Re: knockd can't use ufw

2019-05-08 Thread Dan Streetman
bionic: ubuntu@lp1823051-b:~$ dpkg -l |grep knockd ii knockd 0.7-1ubuntu1.18.04.1 amd64small port-knock daemon May 8 22:16:00 lp1823051-b knockd: openSSH: running command: ufw allow from any to any proto tcp port 1234 May 8 22:16:00 lp1

[Bug 1823051] Re: knockd can't use ufw

2019-05-08 Thread Dan Streetman
cosmic: ubuntu@lp1823051-c:~$ dpkg -l |grep knockd ii knockd 0.7-1ubuntu1.18.10.1amd64 small port-knock daemon May 8 22:08:05 lp1823051-c knockd: openSSH: running command: ufw allow from any to any proto tcp port 1234 May 8 22:08:06 lp1823051-c

[Bug 1823051] Re: knockd can't use ufw

2019-05-08 Thread Dan Streetman
disco verified using steps from test case: ubuntu@lp1823051-d:~$ dpkg -l | grep knockd ii knockd 0.7-1ubuntu2amd64 small port-knock daemon May 8 21:53:45 lp1823051-d knockd: openSSH: running command: ufw allow from any to any proto tcp po

[Bug 1823051] Re: knockd can't use ufw

2019-04-30 Thread Brian Murray
Hello Dan, or anyone else affected, Accepted knockd into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/knockd/0.7-1ubuntu1.18.10.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://

[Bug 1823051] Re: knockd can't use ufw

2019-04-30 Thread Brian Murray
Hello Dan, or anyone else affected, Accepted knockd into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/knockd/0.7-1ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ub

[Bug 1823051] Re: knockd can't use ufw

2019-04-24 Thread Bug Watch Updater
** Changed in: knockd (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823051 Title: knockd can't use ufw To manage notifications about this bug go to: https://

[Bug 1823051] Re: knockd can't use ufw

2019-04-24 Thread Launchpad Bug Tracker
This bug was fixed in the package knockd - 0.7-1ubuntu3 --- knockd (0.7-1ubuntu3) eoan; urgency=medium * d/knockd.service: - Change ProtectSystem to 'true', to allow using ufw in knockd rules (LP: #1823051) - Add CAP_SYS_MODULE so knockd can load iptables modules if ne

[Bug 1823051] Re: knockd can't use ufw

2019-04-24 Thread Dan Streetman
** Bug watch added: Debian Bug tracker #927883 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927883 ** Also affects: knockd (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927883 Importance: Unknown Status: Unknown -- You received this bug notification because

[Bug 1823051] Re: knockd can't use ufw

2019-04-24 Thread Eric Desrochers
Sponsored in 'Eoan' Proposal patch LGTM. https://www.freedesktop.org/software/systemd/man/systemd.exec.html ... ProtectSystem= ... If true, mounts the /usr and /boot directories read-only for processes invoked by this unit. If set to "full", the /etc directory is mounted read-only, too I don't

[Bug 1823051] Re: knockd can't use ufw

2019-04-23 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823051 Title: knockd can't use ufw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/knockd

[Bug 1823051] Re: knockd can't use ufw

2019-04-23 Thread Dan Streetman
** Patch added: "lp1823051-eoan.debdiff" https://bugs.launchpad.net/ubuntu/+source/knockd/+bug/1823051/+attachment/5258212/+files/lp1823051-eoan.debdiff ** Description changed: [impact] any knockd configuration rules that call ufw fail because any ufw changes always update the ufw co

[Bug 1823051] Re: knockd can't use ufw

2019-04-23 Thread Dan Streetman
** Also affects: knockd (Ubuntu Eoan) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823051 Title: knockd can

[Bug 1823051] Re: knockd can't use ufw

2019-04-03 Thread Dan Streetman
** No longer affects: knockd (Ubuntu Ee-series) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823051 Title: knockd can't use ufw To manage notifications about this bug go to: https://bugs.launchpa

[Bug 1823051] Re: knockd can't use ufw

2019-04-03 Thread Dan Streetman
Two possible fixes for this are 1) to add ReadWritePaths=-/etc/ufw to the knockd.service, or 2) change the knockd.service from ProtectSystem=full to ProtectSystem=true. Relaxing the ProtectSystem might actually be the best approach since the only change between 'full' and 'true' is allowing r/w ac