What prevent the generator to use Match/Name instead of
Match/OriginalName by default in .link file like it does for generated
.network files ?
As the few properties that may require a match on the original name
(like set-name) should already use a match directive anyway, so it
should not be an
Still broken in 20.04 beta. This is a real shame…
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724895
Title:
MTU not applied on private ethernet interfaces
To manage notifications about this bug
Still broken on 18.04.03 (netplan 0.97).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724895
Title:
MTU not applied on private ethernet interfaces
To manage notifications about this bug go to:
I don't have any docker, but I'm also using this machine as a NAT
gateway with very high load, and it reliably crash in less than 2
seconds when taking over master role and start handling traffic.
Note that I'm using a pretty basic configuration (NAT only, no bridge,
no fancy network stuff, …)
Look like this is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447
Just for the record: here is the kernel stack trace:
crash> bt
PID: 0 TASK: 82413480 CPU: 0 COMMAND: "swapper/0"
#0 [88807fc037d8] die at 81031d32
#1 [88807fc03808]
I also have issues and as I'm running VM, I managed to get a crash dump
and got this line in GDB:
kernel BUG at /build/linux-5mCauq/linux-4.15.0/net/ipv4/ip_output.c:636
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797386
Title:
[SRU] OpenSSL 1.1.1 to 18.04 LTS
To manage notifications about this bug go
They are required to develop native kresd plugins(We need such plugin in our
infrastructure, but I'm pretty sure very few people need that).
The distributed headers are completely unusable as they use double quotes
instead of angle brackets and IIRC, they even reference headers that are not
Public bug reported:
There is an issue with the mysql plugin that make the server crash
reliably on heavy load.
https://wiki.strongswan.org/issues/2779
This issue was just fixed upstream:
https://git.strongswan.org/?p=strongswan.git;a=commit;h=b3e304258309797dee6dbf561a4bb02b9e11a58b
Would it
Yes. As Bionic is an LTS release, it would be wise to include the
OpenSSL LTS release in it, which is version 1.1.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780807
Title:
Please provide
The undefined __objc symbols are a red herring.
The real curlpribe is the undefined symbol: sk_value also present in the log
and that prevent loading of the __objc classes (trigger the subsequents error
messages).
sk_value is a symbol from OpenSSL.
Simply recompiling the whole packages again
Public bug reported:
When using the HA plugin, charon-systemd try to read
'@{PROC}/@{pid}/net/ipt_CLUSTERIP/' and to write in files into
'@{PROC}/@{pid}/net/ipt_CLUSTERIP/'
So the 2 rules may be append to charon-systemd.apparmor.conf
# Cluster IP
@{PROC}/@{pid}/net/ipt_CLUSTERIP/ r,
Public bug reported:
Using strongswan-systemd (the recommended modern daemon), I can't use
the sql and attr-sql plugins with a mysql backend as it trigger apparmor
errors:
Apr 23 13:25:23 vpn-1 audit[2970]: AVC apparmor="ALLOWED" operation="open"
profile="/usr/sbin/charon-systemd"
Public bug reported:
I'm using strongswan-systemd (charon-systemd package), and each time the
daemon start, there is log in the journal telling that apparmor prevent
the daemon to properly notify systemd.
Apr 20 11:43:09 vpn-2 audit[5970]: AVC apparmor="ALLOWED" operation="sendmsg"
Public bug reported:
libkres-dev installed headers are designed to be used in the knot-
resolver source tree and are unusable when installed in /usr/include.
These headers should either be removed completely or they should be
patched to be usable from elsewhere (using #include instead
of
@Christian
Adding the rc.conf file should be enough but unless you add
/run/systemd/notify w,
unbound won't get far enough to trigger the chown issue.
For the second issue, change the 'deny capability chown,' to 'capability
chown,' in the unbound apparmor profile, restart apparmor and
My config is:
remote-control:
control-enable: yes
control-interface: /var/run/unbound.ctl
The socket created, but then, unbound can't properly change the owner to
unbound:unbound.
Feb 21 13:08:21 linux-agent systemd[1]: Starting Unbound DNS server...
Feb 21 13:08:22
*** This bug is a duplicate of bug 1723900 ***
https://bugs.launchpad.net/bugs/1723900
I disagree with this. While both bugs are related to app armor, they are
not related in any way.
#1723900 is about permission to write in systemd/notify socket, while
this one is about using a local socket
Public bug reported:
When trying to setup unbound to use local socket for unbound-control,
the resulting socket has the wrong owner and the wrong permission, which
make it useless as it requires a root process to use it.
The first issue is that apparmor denies chown to unbound, which result
in a
Public bug reported:
In opendkim-2.10.3, it was possible to define a custom socket path in
/etc/default/opendkim and the systemd.service file was loading it and
using it to define a custom socket path.
In opendkim-2.11, the systemd.service script has been updated and not
only it completely
20 matches
Mail list logo
