On 2023-02-28 18:37, James Lownie wrote:
It sounds like the problem is at our end then, I will investigate further.
Thanks for helping with this Simon.
Great, please let us know how it goes! Thanks
It sounds like the problem is at our end then, I will investigate further.
Thanks for helping with this Simon.
- Original Message -
From: "Simon Deziel"
To: "James Lownie" , 1032...@bugs.debian.org
Sent: Wednesday, 1 March, 2023 10:00:13 AM
Subject: Re: Bug#1032
On 2023-02-28 17:42, James Lownie wrote:
It's not in salsa but it was in my config file. Is it the case that my version
of /etc/apparmor.d/usr.lib.ipsec.charon is different to the package version?
I didn't modify that file manually (apart from moving the lines up in the
file), I did deploy ip
On 2023-02-28 17:12, James Lownie wrote:
Hi Simon, thanks for the suggestion. I'm going to wait and see if other people
can reproduce this before running any tests, this machine is now in production
which makes things awkward. I would have thought putting the secrets in
/etc/ipsec.secrets.d/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2023-02-28 at 16:44 +1100, James Lownie wrote:
> I then modified /etc/apparmor.d/usr.lib.ipsec.charon as follows, after which
> IPSec was able to load the secrets file and authenticate incoming
> connections:
Hi James, thanks for the report.
On 2023-02-28 00:44, James Lownie wrote:
Version: 5.9.1-1+deb11u3
Package: strongswan-charon
Version: 5.9.1-1+deb11u3
Severity: normal
X-Debbugs-Cc: none
Dear maintainer,
Hello James, I'm not maintainer but I've used strongswan with the
Apparmor profiles.
I ran into a problem using Strong
Version: 5.9.1-1+deb11u3
Package: strongswan-charon
Version: 5.9.1-1+deb11u3
Severity: normal
X-Debbugs-Cc: none
Dear maintainer,
I ran into a problem using Strongswan which looks like a bug to me. I'm not
sure if its in strongswan-charon or in Apparmor but I fixed it by editing
/etc/app
7 matches
Mail list logo
