Marking public. CVE requested via oss-security.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/868360
Title:
Incorrect secret key causes user details to be revealed
To manage
http://www.ubuntu.com/usn/usn-1247-1/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/868360
Title:
Incorrect secret key causes user details to be revealed
To manage notifications
CVE-2011-4076 has been assigned for this issue.
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2011-4076
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/868360
Title:
Jurgen, this sounds like you may have not accepted the changes to
/etc/apparmor.d/usr.sbin.mysqld on upgrade. Please look in
/etc/apparmor.d/ for *dpkg* files and merge the changes. If this is not
the case, please file a new bug with 'ubuntu-bug mysql-5.1'. Thanks
--
You received this bug
This should be fixed with http://www.ubuntu.com/usn/usn-1233-1/
** Changed in: krb5 (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to krb5 in Ubuntu.
** Changed in: cobbler (Ubuntu Oneiric)
Status: New = Triaged
** Changed in: cobbler (Ubuntu Precise)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler in Ubuntu.
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Changed in: cobbler (Ubuntu Precise)
Status: New = Triaged
** Changed in: cobbler (Ubuntu Oneiric)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler in Ubuntu.
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
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
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
A workaround for this particular VM is to add the following to
/etc/apparmor.d/libvirt/libvirt-4aa60863-6b03-2f19-897f-4de6d12c96e1 (note that
I expressly did *not* use
/etc/apparmor.d/libvirt/libvirt-4aa60863-6b03-2f19-897f-4de6d12c96e1.files):
Simon,
That's correct. Without testing it, this patch looks fine. Ideally this
would be handled better via the security driver framework, but the
latest git seems to indicate this isn't implemented yet, so this would
be fine for Precise.
So getting this into Ubuntu, the patch should be tested,
This is not fix committed in Ubuntu. A merge with 1:1.2.2-1 from
unstable will fix this issue.
** Changed in: keepalived (Ubuntu)
Status: Fix Committed = Triaged
** Changed in: keepalived (Ubuntu)
Assignee: (unassigned) = Canonical Server Team (canonical-server)
** This bug is no
Removing ubuntu-security-sponsors. tomcat5.5 is processed and tomcat6 is
pending in the security ppa.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat6 in Ubuntu.
https://bugs.launchpad.net/bugs/843701
Title:
CVE-2011-3190
Thank you for reporting this bug to Ubuntu. dapper has reached EOL
(End of Life) and is no longer supported. As a result, this bug
against dapper is being marked Won't Fix. Please see
https://wiki.ubuntu.com/Releases for currently supported Ubuntu
releases.
Please feel free to report any other
Thank you for reporting this bug to Ubuntu. dapper has reached EOL
(End of Life) and is no longer supported. As a result, this bug
against dapper is being marked Won't Fix. Please see
https://wiki.ubuntu.com/Releases for currently supported Ubuntu
releases.
Please feel free to report any other
Thank you for reporting this bug to Ubuntu. dapper has reached EOL
(End of Life) and is no longer supported. As a result, this bug
against dapper is being marked Won't Fix. Please see
https://wiki.ubuntu.com/Releases for currently supported Ubuntu
releases.
Please feel free to report any other
Thank you for reporting this bug to Ubuntu. dapper has reached EOL
(End of Life) and is no longer supported. As a result, this bug
against dapper is being marked Won't Fix. Please see
https://wiki.ubuntu.com/Releases for currently supported Ubuntu
releases.
Please feel free to report any other
Thank you for reporting this bug to Ubuntu. dapper has reached EOL
(End of Life) and is no longer supported. As a result, this bug
against dapper is being marked Won't Fix. Please see
https://wiki.ubuntu.com/Releases for currently supported Ubuntu
releases.
Please feel free to report any other
Thank you for reporting this bug to Ubuntu. dapper has reached EOL
(End of Life) and is no longer supported. As a result, this bug
against dapper is being marked Won't Fix. Please see
https://wiki.ubuntu.com/Releases for currently supported Ubuntu
releases.
Please feel free to report any other
Thank you for reporting this bug to Ubuntu. karmic has reached EOL
(End of Life) and is no longer supported. As a result, this bug
against karmic is being marked Won't Fix. Please see
https://wiki.ubuntu.com/Releases for currently supported Ubuntu
releases.
Please feel free to report any other
Thank you for reporting this bug to Ubuntu. karmic has reached EOL
(End of Life) and is no longer supported. As a result, this bug
against karmic is being marked Won't Fix. Please see
https://wiki.ubuntu.com/Releases for currently supported Ubuntu
releases.
Please feel free to report any other
Thank you for reporting this bug to Ubuntu. dapper has reached EOL
(End of Life) and is no longer supported. As a result, this bug
against dapper is being marked Won't Fix. Please see
https://wiki.ubuntu.com/Releases for currently supported Ubuntu
releases.
Please feel free to report any other
Thank you for reporting this bug to Ubuntu. dapper has reached EOL
(End of Life) and is no longer supported. As a result, this bug
against dapper is being marked Won't Fix. Please see
https://wiki.ubuntu.com/Releases for currently supported Ubuntu
releases.
Please feel free to report any other
Public bug reported:
$ ls -l /etc/apache2/mods-available/suexec.load
-rw-rw-r-- 1 root root 64 2011-09-06 13:38
/etc/apache2/mods-available/suexec.load
While this is not security-relevant, it is also not desirable. What happened is
that the default umask changed fro 0002 to 0022 in 11.10
While this is targeted for Precise, it also is going to need to be
backported to Oneiric as this is a security vulnerability.
** Also affects: cobbler (Ubuntu Oneiric)
Importance: High
Status: New
** Also affects: cobbler (Ubuntu Precise)
Importance: Undecided
Status: New
**
This is not an appropriate rule because it negates the property of guest
isolation. This should be handled dynamically by the security driver,
but it is not (which is the bug). This could be done in a couple of
ways. What are the contents of /var/log/libvirt/qemu/guest1.log after
the AppArmor
Serge,
Not having looked at the file, just dropping a file into
/etc/bash_completion.d is totally fine and is an easy packaging change
without a huge Ubuntu delta. We should send upstream and to Debian, but
I don't think we need to block on it.
--
You received this bug notification because you
** Visibility changed to: Public
** Changed in: puppet (Ubuntu Hardy)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/861182
Title:
Remote
Marking bug as public, since the issue is public now. I have uploaded
untested hardy packages for this and the other CVE that affects hardy to
https://launchpad.net/~ubuntu-security-proposed/+archive/ppa/+packages.
These patches came from upstream and applied cleanly. Since this is in
universe,
Pocket copied puppet to hardy-proposed. Please test and give feedback
here. See https://wiki.ubuntu.com/Testing/EnableProposed for
documentation on how to enable and use -proposed. Thank you in advance!
** Tags removed: security-verification
** Tags added: verification-needed
** Description
To ubuntu-sru: if this passes the verification process, please also
pocket copy to security. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/861182
Title:
Remote directory
) = Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/865462
Title:
Upgrade to 0.25.4-2ubuntu6.3 introduces
http://projects.puppetlabs.com/issues/3922
I uploaded a new puppet for Lucid to the ubuntu-security-proposed ppa
(https://launchpad.net/~ubuntu-security-
proposed/+archive/ppa/+packages). Can someone affected by this bug
comment on if the updated packages fixes the issue?
You can fetch specific binaries at:
** Also affects: puppet (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: puppet (Ubuntu Oneiric)
Importance: High
Assignee: Jamie Strandboge (jdstrand)
Status: In Progress
** Changed in: puppet (Ubuntu Lucid)
Status: New = Fix Committed
I agree the default of nat is appropriate for desktops and I feel quite
strongly it should not change there. The default for servers is probably
better as non-nat (though this could be debated), as this bug suggests.
However having different behavior depending on the type of system it is
would
** Changed in: libvirt (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/865515
Title:
virtual machines should not have nat on servers
To
** This bug has been flagged as a security vulnerability
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/863305
Title:
Image access control is available
To manage notifications about
This should be updated to 2.7.5 or to include the patches in
http://www.ubuntu.com/usn/usn-1223-1/.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/854899
Title:
[FFe] Update to
This should be updated to 2.7.4 or to include the patch in
http://www.ubuntu.com/usn/usn-1217-1/.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/854899
Title:
[FFe] Update to
Public bug reported:
In performing the MIR audit for cobbler-enlist (bug #860492), I
discovred:
- PROBLEM: most xmlrpc_* calls are not doing any error checking, but should be
based on looking at code of xmlrpc-c.
- RECOMMENDATION: create utility function wrappers for the common xmlrpc-c
Public bug reported:
During the review of cobbler-enlist, it was noted that cobbler-enlist doesn't
use SSL. This should be documented as such:
- adjusting the already existing debconf questions/notes to include language
that the information is currently submitted in unencrypted form (and a way
...please feel free to promote and seed once bug #862567 is fixed.
should have read:
...please feel free to seed and promote source and binaries once bug
#862567 is fixed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler-enlist
Marking as 'In Progress' since this is pending bug #862567.
** Changed in: cobbler-enlist (Ubuntu Oneiric)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler-enlist in Ubuntu.
(Ubuntu Oneiric)
Assignee: Jamie Strandboge (jdstrand) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler-enlist in Ubuntu.
https://bugs.launchpad.net/bugs/860492
Title:
[MIR] cobbler-enlist src, cobbler-enlist
Bug #862567 is fixed. Please feel free to seed in main.
** Summary changed:
- [MIR] cobbler-enlist src, cobbler-enlist-udeb bin
+ [MIR] cobbler-enlist source and binaries
** Changed in: cobbler-enlist (Ubuntu Oneiric)
Status: In Progress = Fix Committed
--
You received this bug
** Changed in: libvirt (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/832507
Title:
console.log grows indefinitely
To manage
Unsubscribing ubuntu-security-sponsors since Marc is handling this as
part of his update.
** Changed in: tomcat6 (Ubuntu Lucid)
Status: New = In Progress
** Changed in: tomcat6 (Ubuntu Lucid)
Assignee: (unassigned) = Marc Deslauriers (mdeslaur)
** Changed in: tomcat6 (Ubuntu
Unsubscribing ubuntu-security-sponsors since Steve is handling this as
part of his update.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/813115
Title:
CVE-2011-2202
To manage
Unsubscribing ubuntu-security-sponsors since Steve is handling this as
part of his update.
** Changed in: php5 (Ubuntu Lucid)
Status: Confirmed = In Progress
** Changed in: php5 (Ubuntu Lucid)
Assignee: (unassigned) = Steve Beattie (sbeattie)
** Changed in: php5 (Ubuntu Maverick)
** Changed in: libvirt (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/832507
Title:
console.log grows indefinitely
To manage
** Tags added: apparmor
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu)
Status: New = Triaged
** Changed in: libvirt (Ubuntu)
Importance: Undecided = High
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) = Jamie
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/852885
Title:
PHP rfc1867_post_handler File Path Injection Vulnerability
To manage notifications about
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/852871
Title:
PHP ZEND_SL Opcode Interruption Address Information Leak Vulnerability
To manage
Thank you for using Ubuntu and reporting a bug. More information about
this issue can be found in http://people.canonical.com/~ubuntu-
security/cve/2010/CVE-2010-1864.html
** Changed in: php5 (Ubuntu)
Status: New = Fix Released
** Visibility changed to: Public
--
You received this bug
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/852868
Title:
php5 var_export() information leak
To manage notifications about this bug go to:
Thank you for using Ubuntu and reporting a bug. More information about
this issue can be found in http://people.canonical.com/~ubuntu-
security/cve/2010/CVE-2010-1862.html
** Visibility changed to: Public
** Changed in: php5 (Ubuntu)
Status: New = Fix Released
--
You received this bug
Thank you for using Ubuntu and reporting a bug. More information about
this issue can be found in http://people.canonical.com/~ubuntu-
security/cve/2010/CVE-2010-2190.html
** Visibility changed to: Public
** Changed in: php5 (Ubuntu)
Status: New = Fix Released
--
You received this bug
Thank you for using Ubuntu and reporting a bug. More information about
this issue can be found in http://people.canonical.com/~ubuntu-
security/cve/2010/CVE-2010-2191.html
** Visibility changed to: Public
** Changed in: php5 (Ubuntu)
Status: New = Fix Released
--
You received this bug
** Changed in: php5 (Ubuntu)
Status: New = Confirmed
** Changed in: php5 (Ubuntu)
Assignee: (unassigned) = Steve Beattie (sbeattie)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
Thank you for using Ubuntu and reporting a bug. More information about
this issue can be found in http://people.canonical.com/~ubuntu-
security/cve/2010/CVE-2010-4699.html
** Visibility changed to: Public
** Changed in: php5 (Ubuntu)
Status: New = Fix Released
--
You received this bug
** Changed in: php5 (Ubuntu)
Status: New = Confirmed
** Changed in: php5 (Ubuntu)
Assignee: (unassigned) = Steve Beattie (sbeattie)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
** Changed in: php5 (Ubuntu)
Status: New = Confirmed
** Changed in: php5 (Ubuntu)
Assignee: (unassigned) = Steve Beattie (sbeattie)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
http://permalink.gmane.org/gmane.comp.security.oss.general/3109
** Visibility changed to: Public
** Changed in: php5 (Ubuntu)
Status: New = Confirmed
** Changed in: php5 (Ubuntu)
Assignee: (unassigned) = Steve Beattie (sbeattie)
--
You received this bug notification because you
** Changed in: php5 (Ubuntu)
Status: New = Confirmed
** Changed in: php5 (Ubuntu)
Assignee: (unassigned) = Steve Beattie (sbeattie)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/852910
Title:
PHP Magic Quotes Fails to Protect mysqli_fetch_assoc
To manage notifications about this
Thank you for using Ubuntu and reporting a bug. More information about
this issue can be found in http://people.canonical.com/~ubuntu-
security/cve/2010/CVE-2010-2101.html
** Changed in: php5 (Ubuntu)
Status: New = Fix Released
** Visibility changed to: Public
--
You received this bug
I'll answer my own question, from nova/virt/libvirt/connection.py:
def get_pty_for_instance(instance_name):
virt_dom = self._lookup_by_name(instance_name)
xml = virt_dom.XMLDesc(0)
dom = minidom.parseString(xml)
for serial in
, etc
** Changed in: socat (Ubuntu)
Assignee: Jamie Strandboge (jdstrand) = (unassigned)
** Changed in: socat (Ubuntu)
Status: In Progress = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to socat in Ubuntu.
https
I should mention that performing input validation on
get_pty_for_instance() and dropping privileges would be enough to
'solve' the immediate issues with nova's use of socat, but the other
suggestions are for future-proofing against the new (and presumably
rapidly changing) nova codebase and for
** Changed in: socat (Ubuntu)
Assignee: Ubuntu Security Team (ubuntu-security) = Jamie Strandboge
(jdstrand)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to socat in Ubuntu.
https://bugs.launchpad.net/bugs/829234
Title:
[MIR
I'm still reviewing this, but there is a lot of overlap between socat
and netcat, and I wonder what specific features of socat are required
over netcat.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to socat in Ubuntu.
** Changed in: socat (Ubuntu)
Assignee: Canonical Security Team (canonical-security) = Ubuntu Security
Team (ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to socat in Ubuntu.
https://bugs.launchpad.net/bugs/829234
Thanks Dave. This is satisfactory to the security team. Please continue
to work with upstream on the 'sudoers problem' so that can be resolved
for 12.04.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
** Changed in: nova (Ubuntu)
Assignee: Ubuntu Security Team (ubuntu-security) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/801501
Title:
[MIR] nova
To manage
Kees and I discussed this today, so I will summarize the conversation
(keep in mind I have not reviewed the code personally and Kees only
performed a shallow audit):
* Size and scope: nova is a very large and complex piece of software
with many daemons listening on the network and there is too
This needs an ACK from ubuntu-release at this time. Unsubscribing
ubuntu-sponsors. Once you have the ACK, please resubscribe.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/828789
Thanks Daniel for the debdiff. I am going to NAK this version because the
changelog did not capture all of the changes in the bug:
* debian/munin-node.dirs is updated for upstart
* upstream_bug_832.patch is added
* upstream_add-timeout-to-legal-options.patch is added
Also the following Ubuntu
tomcat7 was fixed in 7.0.21-1.
** Changed in: tomcat6 (Ubuntu)
Status: New = Confirmed
** Changed in: tomcat7 (Ubuntu)
Status: New = Confirmed
** Changed in: tomcat7 (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member
I don't think it is the apparmor security driver code based on where the error
is occurring and the test output:
Test initialization ... (default:default, qemu:///session, apparmor=False) ...
FAIL
The apparmor driver is disabled and it is still failing (granted, in the
session code).
--
You
I should also note I am not actively investigating this issue at
present.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/828792
Title:
[FFE] Merge 0.9.3-5 from debian unstable
To
What specifically were these reasons? When did they no longer become a
concern and why?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
https://bugs.launchpad.net/bugs/840925
Title:
Please make /dev/kvm
** Changed in: kvm (Ubuntu)
Status: New = Incomplete
** Changed in: kvm (Ubuntu)
Assignee: (unassigned) = Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
https
This points to the failure happening before the dynamic profile is
generated.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/828792
Title:
[FFE] Merge 0.9.3-5 from debian unstable
I am happy to report that for the last several weeks this bug seems to
be fixed. It appears to coincide with either linux-firmware 1.60
(possibly 1.59, since I went from 1.58 straight to 1.60) or linux
3.0.0-9.13 (or 3.0.0-9.12). I did updates around 2011-08-23 and found
this bug is no longer a
This is an interesting error:
error: Failed to connect socket to '@/home/tucxnXJm/.libvirt/libvirt-sock':
Connection refused
error: failed to connect to the hypervisor
This is a new location of the socket. Do you have any apparmor denials
in kern.log?
--
You received this bug notification
Sven, what version of libvirt and Ubuntu are you using? Can you attach
the output of 'virsh dumpxml your problem domain'? Thanks
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/607466
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
Marking fixed as per comment #20.
Roy and oliver, if you are still having your issues, please file a new
bug.
** Changed in: dhcp (Ubuntu)
Status: New = Fix Released
** Changed in: dhcp3 (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you
Does this pass QRT?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/828792
Title:
[FFE] Merge 0.9.3-5 from debian unstable
To manage notifications about this bug go to:
This can be added to the apparmor profile to allow -N option to work:
capability sys_nice,
Then run:
$ sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.ntpd
I'm preparing an upload for this policy change now.
--
You received this bug notification because you are a member of Ubuntu
Server
ntp (1:4.2.6.p2+dfsg-1ubuntu11) oneiric; urgency=low
* debian/apparmor-profile: allow sys_nice for -N option to work. More
work is needed to make ntpd start niced, so not auto-closing the bug.
- LP: 229632
--
You received this bug notification because you are a member of Ubuntu
Server
Removing '[natty]' from description as this affects oneiric too, and the
bug is targeted to both natty and oneiric already.
** Summary changed:
- [natty] kvm guests become unstable after a while
+ kvm guests become unstable after a while
--
You received this bug notification because you are a
I'm not up on current mimedefang, but doing something like this would be
even better:
/var/spool/MIMEDefang/mdefang-*/Work/ r,
/var/spool/MIMEDefang/mdefang-*/Work/** r,
If mimedefang's spool directory only contains the files to be scanned,
then the easier to maintain
'/var/spool/MIMEDefang/** r,' looks good. It is similar for what we are
doing with all the others (amavis, havp, etc).
--
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/829089
Title:
Based on Thomas' assessment, should the title of this bug be adjusted
and the apparmor tag removed?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/632696
Title:
libvirt won't start
libvirt has a significant Ubuntu delta, not least of which is adjusting
it for AppArmor, apport, libvirt-migrate-qemu-disks (needed until
12.04), different groups, openiscsi, etc, etc. Glancing at the Debian
changelog, these have not been upstreamed. AFAICT, this should be an FFe
for a merge, not
Serge, but comment #25 by Thomas said he is having the problem even with
AppArmor disabled...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/632696
Title:
libvirt won't start a VM
601 - 700 of 1702 matches
Mail list logo
