Ah, and it looks like the success resolving after reducing the
advertised EDNS UDP packet size pattern got fixed in success resolving
after reducing the advertised EDNS UDP packet size pattern in
http://logwatch.svn.sourceforge.net/viewvc/logwatch/scripts/services/named?r1=1r2=3
.
--
You
** Tags added: regression-release
** Tags removed: regression-potential
--
Current eBox packages in intrepid don't work at all
https://bugs.launchpad.net/bugs/273486
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
--
I reproduced the problem with the original version of nut in the hardy
release, 2.2.1-2.1ubuntu7, and confirmed that upgrading to the version
in hardy-proposed, 2.2.1-2.1ubuntu7.2, corrected this issue. I also
verified that things work properly when:
- upgrading via 2.2.1-2.1ubuntu7 (release) -
** Also affects: dhcp3 (Ubuntu Jaunty)
Importance: High
Status: Incomplete
--
Bad MTU for eth0 in 9.04 amd64
https://bugs.launchpad.net/bugs/352779
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
--
** Changed in: dhcp3 (Ubuntu Jaunty)
Assignee: (unassigned) = Kees Cook (kees)
--
Bad MTU for eth0 in 9.04 amd64
https://bugs.launchpad.net/bugs/352779
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
--
Public bug reported:
Performed a stock install of 8.10 ubuntu-server (i386) with the mail
server task selected and configured to be an internet with smarthost
relay. After fully updating with all intrepid updates and rebooting,
doing an upgrade to jaunty via do-release-upgrade -d resulted in
** Attachment added: dovecot.conf post upgrade.
http://launchpadlibrarian.net/25508604/dovecot.conf
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/25508605/Dependencies.txt
--
dovecot not configured to listen to any ports after intrepid-jaunty upgrade
** Attachment added: /var/log/dist-upgrade/apt-term.log
http://launchpadlibrarian.net/25508745/apt-term.log
--
dovecot not configured to listen to any ports after intrepid-jaunty upgrade
https://bugs.launchpad.net/bugs/361961
You received this bug notification because you are a member of
** Attachment added: /var/log/dist-upgrade/main.log
http://launchpadlibrarian.net/25508751/main.log
--
dovecot not configured to listen to any ports after intrepid-jaunty upgrade
https://bugs.launchpad.net/bugs/361961
You received this bug notification because you are a member of Ubuntu
I just reproduced the dovecot question on a similar amd64 upgrade. Note
that before the upgrade, there exists /etc/dovecot/dovecot.conf and
/etc/dovecot/dovecot.conf.bak that differ like so:
ubu...@iijj-amd64:~$ diff -u /etc/dovecot/dovecot.conf{,.bak}
--- /etc/dovecot/dovecot.conf 2009-04-15
** Tags added: jaunty regression-release
** Tags removed: regression-potential
--
ssh are using ssh-userauth but ignores private key
https://bugs.launchpad.net/bugs/348126
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
I've been unable to reproduce the hanging behavior with apache
configured in a variety of different proxy configurations and beating on
it for quite a while. I have verified that the version in hardy-
proposed, 2.2.8-1ubuntu0.9, also functions when configured to proxy, as
well as continuing to
For the gnutls/hardy SRU:
I have reproduced the acceptance of rsa/md2 v1 certificates by the
version of gnutls13 in hardy-updates, 2.0.4-1ubuntu2.3, and can confirm
that the version of gnutls13 in hardy-proposed does not accept rsa/md2
certificates. I have added a testcase for this situation in
For the openldap/hardy SRU:
I have:
(1) reproduced the acceptance of the v1 certificates as
outlined in Mathias' test case by the ldap clients with ldap
2.4.9-0ubuntu0.8.04.2 and gnutls13 2.0.4-1ubuntu2.
(2) reproduced the rejection of v1 certificates by the ldap clients
Per mdeslaurs (and confirmed by myself), this is still an issue in
jaunty; re-opening.
** Changed in: php5 (Ubuntu Jaunty)
Status: Fix Released = Triaged
--
[SRU] stack smashing detected when calling xmlrpc_set_type
https://bugs.launchpad.net/bugs/239513
You received this bug
I have reproduced the bacula installation error with dbconfig-common
from jaunty, 1.8.40, and can confirm that the version in jaunty-
proposed, 1.8.40ubuntu1, allows bacula to successfully complete
installation. I also installed and purged several other of dbconfig-
common's rdepends and ensured
Martin-Éric, even with APT::Immediate-Configure set to true, I'm unable
to reproduce the failure you see:
$ apt-config dump | grep Immediate
APT::Immediate-Configure true;
$ sudo sh -c 'LC_ALL=C apt-get install libsasl2-2'
Reading package lists... Done
Building dependency tree
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
I can reproduce the pread() failures with clamscan from clamav 0.96.1
+dfsg-0ubuntu0.10.04.1 on lucid; however, all of the files reporting
errors occur on /sys which is the (default) location where the sysfs
filesystem is located. The sysfs filesystem is a synthetic filesystem
that exposes
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
Packages have been pushed to the security ppa and are undergoing
verification.
** Changed in: openldap (Ubuntu)
Status: Confirmed = Fix Committed
** Changed in: openldap (Ubuntu)
Assignee: (unassigned) = Steve Beattie (sbeattie)
--
OpenLDAP Security Fixes?
https
Unfortunately, openldap 2.4.21-0ubuntu5.2 was published in lucid-
security, and so this proposed update needs to be re-uploaded with the
fixes from 2.4.21-0ubuntu5.2 applied.
--
slapd 2.4.21-0ubuntu5 corrupts olcDatabase={-1}frontend.ldif with duplicate
olcAccess lines (again)
This has been released as USN-965-1 and will show up at
http://www.ubuntu.com/usn/usn-965-1. Thanks!
** Changed in: openldap (Ubuntu)
Status: Fix Committed = Fix Released
--
OpenLDAP Security Fixes?
https://bugs.launchpad.net/bugs/610561
You received this bug notification because you are
** Also affects: qemu-kvm (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: qemu-kvm (Ubuntu Lucid)
Status: New = In Progress
** Changed in: qemu-kvm (Ubuntu Lucid)
Importance: Undecided = Medium
--
KVM segmentation fault, using SCSI+writeback and linux 2.4
I've also confirmed that the version of openldap in lucid-proposed,
2.4.21-0ubuntu5.3, does not introduce any regressions in the openldap
tests in lp:qa-regression-testing.
Thanks!
--
slapd 2.4.21-0ubuntu5 corrupts olcDatabase={-1}frontend.ldif with duplicate
olcAccess lines (again)
Jamie: I'm able to reproduce this on Maverick. Here's the output you
requested:
$ dpkg -l | grep mysql
ii libdbd-mysql-perl4.016-1
Perl5 database interface to the MySQL database
ii libmysqlclient16 5.1.49-1ubuntu2
** Changed in: mysql-5.1 (Ubuntu)
Status: Incomplete = Triaged
--
AppArmor complains about missing local/usr.sbin.mysqld file
https://bugs.launchpad.net/bugs/616417
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in
Umm, surely this is the problem:
]$ dpkg -L apparmor | grep local
/etc/apparmor.d/local
/etc/apparmor.d/local/README
--
AppArmor complains about missing local/usr.sbin.mysqld file
https://bugs.launchpad.net/bugs/616417
You received this bug notification because you are a member of Ubuntu
Server
Ah, no, you've been pushing the generation of local/ files into the
postinst packages with the profiles themselves. The issue is that mysql-
server-5.1's postinst doesn't contain the dh_apparmor generated bits to
create it.
(Can dh_apparmor be used here? The mysqld apparmor policy is reloaded as
The upstart runlevel issue was fixed for maverick in 5.1.48-1ubuntu5
which referenced bug 608423. On Lucid, my understanding is that the typo
existed only in a version uploaded to lucid-proposed, and that it was
corrected before being promoted to lucid-updates. Therefore I am closing
this bug.
Public bug reported:
Attempting to run the mysql testsuite fails with the apparmor policy as
shipped in maverick with the following rejection:
[72565.740926] type=1400 audit(1281713173.741:61): apparmor=DENIED
operation=file_mmap parent=18416 profile=/usr/sbin/mysqld
Public bug reported:
Attempting to run the testsuite from the version in maverick
(5.1.49-1ubuntu4) fails like so:
$ cd /usr/lib/mysql-testsuite ; ./mysql-test-run.pl --vardir=$(mktemp -d
/tmp/mysql-test-XXX)
Logging: ./mysql-test-run.pl --vardir=/tmp/mysql-test-qbhh5Yy8FwS
100813
Here's the dpatch I created which causes the basic testsuite to pass
both at build time and post-installation.
** Attachment added: 99_fix_testsuite_for_installed_env.dpatch
From the dpkg-terminal log:
Unpacking mysql-server-5.1 (from
.../mysql-server-5.1_5.1.41-3ubuntu12_i386.deb) ...
debconf: DbDriver config: /var/cache/debconf/config.dat is locked by another
process: Resource temporarily unavailable
dpkg: error processing
This was fixed in maverick's mysql-5.1 in bug 617463. It probably should
be considered for an SRU for Lucid.
--
MySQL cannot access it's plugin directory (AppArmor rule)
https://bugs.launchpad.net/bugs/594932
You received this bug notification because you are a member of Ubuntu
Server Team,
Alas, it seems that the attached DpkgTerminalLog.txt only contains the
logs from your attempts to fix the issue. Is it possible to attach the
contents of /var/log/apt/term.log, as that my contain the actual
failure?
Thanks.
--
package mysql-server-5.1 5.1.41-3ubuntu12.3 failed to
** Changed in: mysql-dfsg-5.1 (Ubuntu)
Status: New = Incomplete
--
package mysql-server-5.1 5.1.41-3ubuntu12.3 failed to install/upgrade: Package
is in a very bad inconsistent state - you should reinstall it before
attempting a removal.
https://bugs.launchpad.net/bugs/619520
You
Thanks, Clint! I've fixed up the test script in lp:qa-regression-testing
to take all this into account.
--
MySQL must not use /tmp
https://bugs.launchpad.net/bugs/375371
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in
Public bug reported:
Binary package hint: whois
The recent sync of whois is lacking a conflicts/replaces with the
mkpasswd package, which was separated out by ubuntu in the lucid cycle
to fix bug 284416. However, it was decided in bug 601803 to resume
syncing whois with debian, but this breaks
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/632791/+attachment/1555446/+files/Dependencies.txt
--
upgrade fails: trying to overwrite '/usr/bin/mkpasswd', which is also in
package mkpasswd 5.0.6ubuntu1
https://bugs.launchpad.net/bugs/632791
You received this bug
Unfortunately, we can't just sync from debian because we published a
separate mkpasswd package during the lucid cycle and thus people
upgrading will see the failure in bug 632791.
--
when whois and mkpasswd are build locally they have .mo file conflicts
https://bugs.launchpad.net/bugs/601803
You
Attached is a debdiff to add replaces: mkpasswd. I've verified that it
fixes the broken upgrade issue on a couple of hosts that have hit the
issue.
** Patch added: whois_5.0.7ubuntu1.debdiff
Thanks for the feedback, Colin. Updated debdiff attached.
** Patch added: whois_5.0.7ubuntu1.debdiff
https://bugs.launchpad.net/ubuntu/+source/whois/+bug/632791/+attachment/1558648/+files/whois_5.0.7ubuntu1.debdiff
--
upgrade fails: trying to overwrite '/usr/bin/mkpasswd', which is also in
** Visibility changed to: Public
--
php5 crashed with SIGSEGV in sapi_header_op()
https://bugs.launchpad.net/bugs/635664
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in ubuntu.
--
Ubuntu-server-bugs mailing list
Chuck, I'm seeing very similar things in maverick (upgraded from lucid):
$ php5 -v
PHP Warning: PHP Startup: Unable to load dynamic library
'/usr/lib/php5/20090626/ldap.so' - /usr/lib/php5/20090626/ldap.so: cannot open
shared object file: No such file or directory in Unknown on line 0
PHP
Hi Jeff,
Are you seeing the hangs with your local connections or just with
connections to the DC? Does the ssh client respond to the escape
character (defaults to ~); that is, with the default configuration will
sending '~.' kill the connection? Does strace or ssh -vv (or more vs)
show anything
** Visibility changed to: Public
--
list_lists crashed with ImportError in module()
https://bugs.launchpad.net/bugs/436795
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mailman in ubuntu.
--
Ubuntu-server-bugs mailing list
** Changed in: vm-builder (Ubuntu)
Importance: Undecided = Medium
--
vm-builder images and configuration files should not be world readable
https://bugs.launchpad.net/bugs/386463
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Colin, people who upgraded from jaunty to karmic and did the test out
grub2 will probably have both grub and grub2 installed (that is at least
the situation with one of my hosts). Unfortunately, update-manager
andapt-getdist-upgrade is resolving the added conflict in
Public bug reported:
Binary package hint: logwatch
Logwatch currently does not report any information about apparmor events
in its generated emails; this should be added.
** Affects: logwatch (Ubuntu)
Importance: Undecided
Status: New
--
logwatch should report apparmor events
** Tags added: karmic regression-release
** Tags removed: regression-potential
--
libvirtError: operation failed: could not query memory balloon allocation
https://bugs.launchpad.net/bugs/456602
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
Binary package hint: ntp
For some reason, the timeadj binary in the ntp package doesn't appear to
get built with gcc's stack protector option. Running the hardening check
from the qa-regression-testing testsuite doesn't find the
__stack_chk_fail symbol.
** Attachment added: .etc.apparmor.d.usr.sbin.ntpd.txt
http://launchpadlibrarian.net/38731990/.etc.apparmor.d.usr.sbin.ntpd.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/38731991/Dependencies.txt
** Attachment added: KernLog.txt
I am able to reproduce the generated output when rotating logs with the
version of python-image-store-proxy in karmic, 1.0.4-0ubuntu1, and can
confirm that the version in karmic-proposed, 1.0.4-0ubuntu1.1, fixes the
issue. I don't have a eucalyptus setup, so I am unable to test the
package in that
= Medium
** Changed in: clamav (Ubuntu)
Assignee: (unassigned) = Steve Beattie (sbeattie)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in Ubuntu.
https://bugs.launchpad.net/bugs/1420819
Title:
ClamAV 0.98.6 security
Hi Chris,
Did you do a test build on powerpc? Even with not using llvm, I got a
build failure in the unit tests on powerpc. I'll retry the build as
sometimes things can be flaky on the powerpc buildds, but the relevant
bits from the log are as follows:
make[3]: Entering directory
I think I see this as well, simply doing an 'apt-get install mysql-
server-5.6' on vivid leaves things in the following state after the
installation completes:
$ sudo aa-status
[SNIP]
2 processes are unconfined but have a profile defined.
/usr/sbin/dnsmasq (665)
/usr/sbin/mysqld
This was addresses in http://www.ubuntu.com/usn/usn-2461-1/ , thanks.
** Changed in: libyaml (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libyaml in Ubuntu.
** Tags removed: apparmor
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1100877
Title:
lxc-start fails after upgrade to raring
To manage notifications about this bug go to:
So python-oauth2 has some reverse dependencies:
python-oauth2
Reverse Depends:
turses
screenlets-pack-all
python-django-social-auth
python-django-oauth-plus
turses was removed from debian in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779448
python-django-social-auth was removed
Here's the complete sh -xe output from running lxc-net start:
ubuntu@vivid-i386:~$ sudo sh -xe /usr/lib/i386-linux-gnu/lxc/lxc-net start
+ distrosysconfdir=/etc/default
+ localstatedir=/var
+ varrun=/run/lxc
+ USE_LXC_BRIDGE=true
+ LXC_BRIDGE=lxcbr0
+ LXC_ADDR=10.0.3.1
+ LXC_NETMASK=255.255.255.0
Public bug reported:
The lxc-net script in /usr/lib/$archtriplet/lxc/lxc-net attempts to use
ifconfig first and then falls back to trying to use ip(8) in the ifup()
and ifdown() shell functions. This behavior should be reversed, as ip
has been preferred over ifconfig for several years now.
As an
And here's the patch to the lxc-net script to prefer ip(8) over
ifconfig.
** Patch added: lxc-net-prefer_ip.patch
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424143/+attachment/4323815/+files/lxc-net-prefer_ip.patch
--
You received this bug notification because you are a member of
So the only difference that I can see is that so *without* the added
remount rule, /proc/mounts contains the following entries for
sysfs+/sys/ within the container:
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
sysfs /sys sysfs ro,nosuid,nodev,noexec,relatime 0 0
with the added rule,
Public bug reported:
When starting up an ubuntu lxc container in vivid, I'm seeing the
following apparmor rejection:
Feb 21 01:30:41 vivid-i386 kernel: [ 2121.606513] audit: type=1400
audit(1424511041.643:125): apparmor=DENIED operation=mount
info=failed flags match error=-13
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
*** This bug is a duplicate of bug 1438745 ***
https://bugs.launchpad.net/bugs/1438745
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1438745, so it is being marked as such. Please
** Package changed: openssh (Ubuntu) = xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1450871
Title:
xserver crashes ATI AMD Radeon 7700 driver 12.20
To manage
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers in Ubuntu.
https://bugs.launchpad.net/bugs/1441369
Title:
package init-system-helpers 1.22ubuntu5 failed
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
Seems to be a dependency conflict that is causing both postfix and exim4
to be installed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to exim4 in Ubuntu.
https://bugs.launchpad.net/bugs/1483341
Title:
package exim4-config (not
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
dhcp3 was superceded by isc-dhcp between lucid and precise and therefore
is not available under any supported ubuntu release. Marking the task
dhcp3 as Won't Fix.
** Changed in: dhcp3 (Ubuntu)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of
dhcp3 was superceded by isc-dhcp between lucid and precise and therefore
is not available under any supported ubuntu release. Marking the task
dhcp3 as Won't Fix.
** Changed in: dhcp3 (Ubuntu)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of
dhcp3 was superceded by isc-dhcp between lucid and precise and therefore
is not available under any supported ubuntu release. Marking the task
dhcp3 as Won't Fix.
** Changed in: dhcp3 (Ubuntu)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of
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
This has been addressed in all supported Ubuntu releases, closing.
** Changed in: asterisk (Ubuntu)
Status: Confirmed = Fix Released
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Server Team,
This has been addressed in all supported releases of Ubuntu, closing.
** Changed in: asterisk (Ubuntu)
Status: Confirmed = Fix Released
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Server
This has been addressed in all supported Ubuntu releases. closing.
** Changed in: asterisk (Ubuntu)
Status: Confirmed = Fix Released
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Moving this back to lxc, as this doesn't appear to be an apparmor
problem.
** Package changed: apparmor (Ubuntu) = lxc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1446658
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
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
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
Packages to address the issue in lxc are currently building in the
ubuntu-security-proposed ppa: https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/ ; please test these when they complete to
verify that there aren't any additional regressions that have cropped up
in this update.
Mitre assigned CVE-2015-8709 for this issue.
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-8709
** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-8550
** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-8551
** CVE removed:
** Description changed:
- A kernel bug in user namespaces allows root in a container to ptrace
- host-root-owned tasks during a window of opportunity during lxc-attach /
- 'lxc exec', before they drop privilege by doing setuid to the container
- root uid.
+ ** DISPUTED ** kernel/ptrace.c in the
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
AF_UNSPEC is used in calls to getaddrinfo(3) to request either ipv4 or
ipv6 addresses. In the parser, we've been filtering out AF_UNSPEC as an
option. It's a simple enough patch to enable it:
Index: b/common/Make.rules
===
---
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 - 191 of 191 matches
Mail list logo
