** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libgsm in Ubuntu.
https://bugs.launchpad.net/bugs/1860414
Title:
ZDI-CAN-9867: Canonical libgsm AssertFailure
Has this been reported to the upstream libgsm developers?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libgsm in Ubuntu.
https://bugs.launchpad.net/bugs/1860414
Title:
ZDI-CAN-9867: Canonical libgsm AssertFailure
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Since the package referred to in this bug is in universe or
multiverse, it is community maintained. If you are able, I suggest
coordinating with upstream and posting a debdiff for this issue. When a
debdiff is
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1706770
Title:
Lock screen can be bypassed when
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1862933
Title:
Apport crash report & cron script
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1862348
Title:
Apport lock file root privilege
Public bug reported:
Placeholder to start preparing SRU for
https://github.com/snapcore/core20/issues/48
** Affects: libseccomp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
See attached for a debdiff to fix this in groovy - this backports the PR
mentioned above to add these missing syscalls for aarch64.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
For the issue of not being able to save files to / from external drives,
you need to manually connect the removable-media interface for the
audacity snap - so either in Ubuntu Software search again for audacity
and then via the 'Permissions' button ensure the 'Read/write files on
removable storage
@jdstrand would you be willing to sponsor that for me to groovy and then
I'll update this bug for SRU of this back to focal (and will add this
change also for the existing libseccomp SRU for eoan/bionic/xenial in LP
#1876055)
--
You received this bug notification because you are a member of
** Patch added: "libseccomp_2.4.3-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633/+attachment/5370131/+files/libseccomp_2.4.3-1ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Tested on an up-to-date groovy install:
amurray@sec-groovy-amd64:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
Codename: groovy
amurray@sec-groovy-amd64:~$ dpkg -l seccomp
When generating the list of systems calls for aarch64, libseccomp uses
the generic kernel API headers rather than the architecture specific
ones - and so misses the definitions of getrlimit, setrlimit and clone3
for aarch64 - if this is changed to use arch-specific headers then we
can regenerate
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1878177
Title:
CVE-2020-3810 out-of-bound stack reads in
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
gnome-shell is responsible for the lock screen so reassigning to that
** Package changed: shadow (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
One more thing - I expect your phone has USB Tethering enabled - and so
presents itself as an rndis USB/ethernet device - and then network
manager uses this as a preferred interface to route traffic through
rather than the wireless interface.
--
You received this bug notification because you are
This doesn't seem like a security issue to me - I believe this is the
default behaviour when using network manager for tethering - it will
route traffic via the tethered device. I am reassigning this against
network-manager which is likely doing the route setup.
** Information type changed from
This was fixed in the https://launchpad.net/ubuntu-cve-tracker in commit
https://git.launchpad.net/ubuntu-cve-
tracker/commit/?id=6d3a00335ca58346a10a09ad3c94046820490f8f
** No longer affects: krb5 (Ubuntu)
** No longer affects: krb5 (Ubuntu Bionic)
** Changed in: krb5 (Ubuntu Focal)
Apologies for posting the description as a comment above...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1895060
Title:
[FFe] apparmor 3 upstream release
Status in
As per the draft upstream release notes:
AppArmor 3.0 is a major new release of the AppArmor user space that makes
an important change to policy development and support. Its focus is
transitioning policy to the new features ABI and as such other new features
have been limited.
Apprmor 3.0 is a
** Attachment added: "groovy-proposed-apparmor-install.log"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895060/+attachment/5411197/+files/groovy-proposed-apparmor-install.log
** Description changed:
As per the draft upstream release notes:
AppArmor 3.0 is a major new
I can't see any potential security impact from this - yes it will now do
another round of asking for passwords but 9 tries doesn't really help
(from an attacker point-of-view) any more than 6 tries assuming this is
a long passphrase - so consider this an ACK from the security team.
--
You
I was planning on doing an SRU to backport
b3206ad5645dceda89538ea8acc984078ab697ab for openat2 etc anyway so
assigning this to me.
** Changed in: libseccomp (Ubuntu)
Assignee: (unassigned) => Alex Murray (alexmurray)
--
You received this bug notification because you are a member of Ubu
This is now passing:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-
groovy/groovy/amd64/a/apparmor/20200921_175620_e825f@/log.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Good point about the changelog - I have removed that line and rebuilt.
Attaching the debdiff here for the release team to review.
** Patch added: "iptables_1.8.5-3ubuntu1.debdiff"
I have done the merge and uploaded it to the security-proposed PPA -
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa -
and have confirmed the iptables autopkgtest tests all pass as well as
the ufw tests.
Oibaf - since you requested this, would you be able to also test this?
Christian - thanks for your work on debugging this - can you please
remove the block-proposed tag if you are happy that 3.0.0~beta1-0ubuntu6
resolves this issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
See attached for a debdiff (note this uses ubuntu3 instead of ubuntu2
since I already burned that version in the security-proposed PPA whilst
preparing this)
** Patch added: "nss_3.55-1ubuntu3.debdiff"
Public bug reported:
As per the archive test rebuild done recently by doko, nss FTBFS due to
a compiler warning raised by gcc-10 (and this fails the build due to the
use of -Werror in CFLAGS):
https://launchpad.net/ubuntu/+archive/test-
rebuild-20200925-groovy/+build/20033437
nsinstall.c: In
This has also been uploaded to the security-proposed PPA -
https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+sourcepub/11635176/+listing-archive-extra
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in
** Also affects: libseccomp (Ubuntu Groovy)
Importance: Medium
Status: New
** Also affects: libseccomp (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: libseccomp (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: libseccomp (Ubuntu
** Description changed:
[Impact]
- snap-confine from snapd uses libseccomp to filter various system calls
- for confinement. The current version in eoan/bionic/xenial (2.4.1) is
- missing knowledge of various system calls for various architectures. As
- such this causes strange issues like
** Summary changed:
- SRU: Backport 2.4.3-1ubuntu2 from groovy to focal/eoan/bionic/xenial for
newer syscalls for core20 base
+ SRU: Backport 2.4.3-1ubuntu3 from groovy to focal/eoan/bionic/xenial for
newer syscalls for core20 base and test suite robustness
--
You received this bug
** Summary changed:
- SRU: Backport 2.4.3-1ubuntu1 from focal to eoan/bionic/xenial for newer
syscalls for core20 base
+ SRU: Backport 2.4.3-1ubuntu2 from groovy to focal/eoan/bionic/xenial for
newer syscalls for core20 base
--
You received this bug notification because you are a member of
** Description changed:
- Placeholder to start preparing SRU for
- https://github.com/snapcore/core20/issues/48
+ [Impact]
+
+ snap-confine from snapd uses libseccomp to filter various system calls
+ for confinement. The current version in eoan/bionic/xenial (2.4.1) is
+ missing knowledge of
** Patch added: "focal"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5374693/+files/libseccomp_2.4.3-1ubuntu3.20.04.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in
** Patch added: "xenial"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5374696/+files/libseccomp_2.4.3-1ubuntu3.16.04.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in
** Patch added: "bionic"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5374695/+files/libseccomp_2.4.3-1ubuntu3.18.04.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in
** Patch added: "eoan"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5374694/+files/libseccomp_2.4.3-1ubuntu3.19.10.1.debdiff
** Patch removed: "Update for groovy solely to add the test suite change to be
in-line with older releases"
** Patch removed: "focal"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5374693/+files/libseccomp_2.4.3-1ubuntu3.20.04.1.debdiff
** Patch removed: "eoan"
** Patch added: "libseccomp_2.4.3-1ubuntu3.20.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5374699/+files/libseccomp_2.4.3-1ubuntu3.20.04.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Patch added: "groovy"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5374698/+files/libseccomp_2.4.3-1ubuntu3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
Yes (barring bugs), there is no intention to break anything :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1895060
Title:
[FFe] apparmor 3 upstream release
Status in
Thanks for the debdiff - I am happy to sponsor this for you - one quick
thing, there is no need to reference the debian bug report in the
changelog so I have cleaned it up to look like the following:
ntp (1:4.2.8p10+dfsg-5ubuntu7.3) bionic-security; urgency=medium
* SECURITY UPDATE: Null
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1895839
Title:
CVE-2020-24977
Status in libxml2
How are your users connecting to the X server? From the description you
mention lightdm - can you explain the setup and I will see if I can
reproduce it?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib-networking in
** Changed in: glib-networking (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib-networking in Ubuntu.
https://bugs.launchpad.net/bugs/1890047
Title:
Sessions crash, all X11
Ok, since I can't reproduce this locally, if you are interested / able
to help with debugging it, could you please attach the core dump. Or if
this contains potentially sensitive details, you could install the dbg
versions of the packages and reproduce the crash and this would provide
a more
I am confused - in the initial bug report you mention
/etc/systemd/system/dbus-org.freedesktop.resolve1.service as the systemd
unit but now you also mention /etc/systemd/system/dbus-
org.freedesktop.ModemManager1.service - can you confirm which one you
have had to disable the SystemCallFilter?
You can specify the package name using `-p` - so perhaps:
apport-collect -p systemd 1886115
apport-collect -p libseccomp2 1886115
Would do the trick?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Thanks for reporting this issue. I am not able to reproduce it myself -
have you customised the syscall filtering in this profile at all?
** Changed in: libseccomp (Ubuntu)
Assignee: (unassigned) => Alex Murray (alexmurray)
--
You received this bug notification because you are a mem
To capture some more details that might help debug this issue, could you
please run
apport-collect 1886115
in a terminal? This should automatically capture various details and
upload them to this bug report.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
If this is indeed related to the Gentoo bug, I cannot see anywhere in
libseccomp where the environment is being modified. As such I suspect
this is likely actually a bug in systemd where it is modifying the
environment across the exec() and the libseccomp update has just caused
it to actually
I am not sure how packages.ubuntu.com generates its list but they were
published for all architectures on launchpad:
https://launchpad.net/ubuntu/+source/libseccomp/2.4.3-1ubuntu3.20.04.2
Also the debs are present on ports.ubuntu.com: http://ports.ubuntu.com
The systemd update for eoan is not in -proposed but the libseccomp
updates (for all releases) are - the systemd update for eoan needs to be
released in conjunction with the libseccomp update as it fixes a
regression in systemd/eoan/i386 when used in conjunction with the
libseccomp updates.
The
@ddstreet - is there anything I can / still need to do to get this into
-updates?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1877633
Title:
libseccomp 2.4.3 (and
Ping @jdstrand / @sil2100 - I am not sure what more I need to do to try
and progress this SRU - I believe the systemd/eoan update still needs to
be sponsored from the security-proposed PPA - but I don't have
permission to upload this myself - could one of you please do that on my
behalf? Also if
@jdstrand - thanks but unfortunately that version FTBFS on arm64 - I've
uploaded an updated verion (ubuntu3.11 -
https://launchpadlibrarian.net/484321608/systemd_242-7ubuntu3.11_source.changes)
to the security-proposed PPA with an additional upstream fix for the
arm64 FTBFS - this is currently
Yes, like previous libseccomp updates, we plan to publish this to both
-security and -updates.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1876055
Title:
SRU: Backport
Ah thanks Dan! - I realise now that perhaps I should have had just the 1
bug report for both issues to make things simpler as having two seems to
have complicated things too much.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
systemd-242-7ubuntu3.11 passes autopkgtest for eoan/i386 and resolves
the FTBFS for arm64 -
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-eoan-ubuntu-security-proposed-
ppa/eoan/i386/s/systemd/20200615_102850_82300@/log.gz
@jdstrand can you
Successful test log for seccomp 2.4.3-1ubuntu3.16.04.2 from xenial-
proposed
** Attachment added: "libseccomp-xenial-proposed-test.log"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5382294/+files/libseccomp-xenial-proposed-test.log
** Tags removed:
Successful test log for seccomp 2.4.3-1ubuntu3.20.04.2 from focal-
proposed
** Attachment added: "libseccomp-focal-proposed-test.log"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5382297/+files/libseccomp-focal-proposed-test.log
** Tags removed:
Successful test log for seccomp 2.4.3-1ubuntu3.19.10.2 from eoan-
proposed
** Attachment added: "libseccomp-eoan-proposed-test.log"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5382296/+files/libseccomp-eoan-proposed-test.log
** Tags removed:
Successful test log for seccomp 2.4.3-1ubuntu3.18.04.2 from bionic-
proposed
** Attachment added: "libseccomp-bionic-proposed-test.log"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5382295/+files/libseccomp-bionic-proposed-test.log
** Tags removed:
Verified on xenial/bionic/eoan/focal as follows:
# install seccomp
$ apt install seccomp
# try resolving getrlimit for aarch64
$ scmp_sys_resolver -a aarch64 getrlimit
# on the current focal version this fails to resolve correctly and returns
-10180
# on other releases this succeeds as
Verified on focal using the following procedure - full log attached as
well:
# install seccomp
$ apt install seccomp
# try resolving getrlimit for aarch64
$ scmp_sys_resolver -a aarch64 getrlimit
-10180
# on the current focal version this fails to resolve correctly and
returns -10180
# enable
I can reproduce the systemd eoan/i386 autopkgtest failure locally - this
is similar to LP #1853852 - testing a rebuild of systemd 242-7ubuntu3.9
with the patch from that bug backported.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Attachment added:
"systemd-242-7ubuntu3.10-i386-autopkgtest-libseccomp-proposed-upgrade.log.gz"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5383166/+files/systemd-242-7ubuntu3.10-i386-autopkgtest-libseccomp-proposed-upgrade.log.gz
--
You received this
** Patch added: "systemd_242-7ubuntu3.10.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5383164/+files/systemd_242-7ubuntu3.10.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
I have confirmed the attached debdiff for systemd resolves this failure
on i386 with libseccomp 2.4.3 - see attached for the autopkgtest log of
a local run.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in
@jdstrand - could you please review and sponsor the systemd debdiff to
eoan-proposed?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1876055
Title:
SRU: Backport
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: systemd (Ubuntu Xenial)
** No longer affects: systemd (Ubuntu Bionic)
** No longer affects: systemd (Ubuntu Focal)
** No longer affects: systemd (Ubuntu Groovy)
--
You received this bug
Thanks - in Ubuntu releases 18.04 onwards debug symbols are provided via
the separate -dbgsyms packages which require extra configuration -
https://wiki.ubuntu.com/DebuggingProgramCrash
TL;DR:
echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe
multiverse" | sudo tee
** Also affects: iptables (Ubuntu Hirsute)
Importance: Undecided
Assignee: Alex Murray (alexmurray)
Status: Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1898547
Title:
neutron-linuxbridge-agent fails to start with iptables 1.8.5
Status
Public bug reported:
I have configured apt-src access to the private ESM PPAs via entries in
/etc/apt/sources.list.d/ubuntu-security.list as follows:
deb-src https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-
security/ubuntu trusty main
and then added credentials as follows to
jdstrand sponsored this to groovy-proposed and autopkgtests have all
passed - ~ubuntu-sru - could you please review?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1898547
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
@rokclimb15 - are you still looking at producing debdiff's for focal +
groovy as well?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1891953
Title:
CVE-2019-8936
Status in
Excellent - thank you :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1891953
Title:
CVE-2019-8936
Status in ntp package in Ubuntu:
Confirmed
Status in ntp source
Yep I'll take this @Christian
** Changed in: iptables (Ubuntu Groovy)
Assignee: (unassigned) => Alex Murray (alexmurray)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.
** Changed in: iptables (Ubuntu Groovy)
Assignee: (unassigned) => Alex Murray (alexmurray)
** Changed in: iptables (Ubuntu Hirsute)
Assignee: (unassigned) => Alex Murray (alexmurray)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Changed in: iptables (Ubuntu Groovy)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1898547
Title:
neutron-linuxbridge-agent
** Description changed:
- Ubuntu Groovy (20.10)
- kernel 5.8.0-20-generic
- neutron-linuxbridge-agent: 2:17.0.0~git2020091014.215a541bd4-0ubuntu1
- iptables: 1.8.5-3ubuntu1 (nf_tables)
- iptables-restore points to xtables-nft-multi
+ [Impact]
- After upgrading iptables from 1.8.4 to 1.8.5 and
** Description changed:
[Impact]
With iptables 1.8.5 neutron-linuxbridge-agent fails to properly start.
The log file shows many errors like:
2020-10-05 10:20:37.998 551 ERROR
neutron.plugins.ml2.drivers.agent._common_agent ; Stdout: ; Stderr:
iptables-restore: line 29 failed
FYI the two autopkgtest failures for arm64 (sshuttle & firewalld) both
appear to be transient failures so these are currently being retried...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
As noted in the discourse thread on this https://discourse.ubuntu.com/t
/private-home-directories-for-ubuntu-21-04-onwards/19533 - I think a
similar ACL approach should be able to be used to give the www-data user
or similar access to your home dir for ~/public_html or for samba as
needed.
--
*** This bug is a duplicate of bug 48734 ***
https://bugs.launchpad.net/bugs/48734
** This bug has been marked a duplicate of bug 48734
Home permissions too open
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to adduser
I have packages for 2.5.1 in the ubuntu-security-proposed PPA at
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa if
you would like to give them a try I would appreciate any feedback etc.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
s: Fix Committed => Fix Released
** Changed in: shadow (Ubuntu Hirsute)
Assignee: (unassigned) => Alex Murray (alexmurray)
** Changed in: adduser (Ubuntu Hirsute)
Assignee: (unassigned) => Alex Murray (alexmurray)
--
You received this bug notification because you are a member of Ubun
*** This bug is a duplicate of bug 1908818 ***
https://bugs.launchpad.net/bugs/1908818
** This bug has been marked a duplicate of bug 1908818
pure packaging of libnss3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
101 - 200 of 340 matches
Mail list logo
