This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu1 --------------- lxc (0.8.0~rc1-4ubuntu1) quantal; urgency=low
* Merge from unstable. Remaining changes: - control: - update maintainer - Build-Depends: add dh-apparmor and libapparmor-dev - lxc Depends: add bridge-utils, dnsmasq-base, iptables, rsync - lxc Recommends: add cgroup-lite | cgroup-bin, openssl - lxc Suggests: add btrfs-tools, lvm2, qemu-user-static - lxc Conflicts: remove (cgroup-bin) - Add lxc-start-ephemeral and lxc-wait to debian/local - apparmor: - add lxc.apparmor, lxc-containers.apparmor, lxc-default.apparmor, and new lxc.apparmor.in - add debian/lxc.conf (default container creation config file) - debian/lxc.install.in: * add lxc-start-ephemeral * add debian/lxc.conf * skip lxc-debconf* * skip lxc-ls (Use upstream's) - debian/lxc*.install.in: use '*', not @DEB_HOST_MULTIARCH@ - Use our own completely different lxc.postinst and lxc.postrm - remove lxc.templates - debian/rules: * add DEB_DH_INSTALLINIT_ARGS = --upstart-only * don't do debconf stuff * add debian/*.apparmor.in to files processed under override_dh_auto_clean * don't comment out ubuntu or busybox templates * do apparmor stuff and install our own lxc-wait under override_dh_install * install our upstart scripts in override_dh_installinit - add lxc.default, lxc.lxc-net.upstart, lxc.upstart under debian/ * patches kept: - 0013-lxc-create-use-default-config.patch (needed manual rebase) - 0030-ubuntu-template-fail.patch - 0031-ubuntu-template-resolvconf.patch - 0044-lxc-destroy-rm-autos - debian/patches/0045-fix-other-templates - debian/patches/0046-lxc-clone-change-hwaddr - debian/patches/0047-bindhome-check-shell - debian/patches/0049-ubuntu-template-sudo-and-cleanup - debian/patches/0050-clone-lvm-sizes - debian/patches/0052-ubuntu-bind-user-conflict - debian/patches/0053-lxc-start-pin-rootfs - debian/patches/0054-ubuntu-debug - debian/patches/0055-ubuntu-handle-badgrp - debian/patches/0056-dont-watch-utmp - debian/patches/0057-update-manpages - debian/patches/0058-fixup-ubuntu-cloud - debian/patches/0059-reenable-daily-cloudimg - debian/patches/0060-lxc-shutdown - debian/patches/0061-lxc-start-apparmor - debian/patches/0062-templates-relative-paths - debian/patches/0063-check-apparmor-enabled - debian/patches/0064-apparmor-mount-proc - debian/patches/0065-fix-bindhome-relpath - debian/patches/0066-confile-typo - debian/patches/0067-templates-lxc-profile - debian/patches/0068-fix-lxc-config-layout - debian/patches/0069-ubuntu-cloud-fix - debian/patches/0070-templates-rmdir-dev-shm - debian/patches/0071-ubuntu-cloud-fix-image-extraction - debian/patches/0072-lxc-shutdown-help - debian/patches/0073-lxc-destroy-waits-before-destroy - mark all patches which have been forwarded as such, refresh all * 0074-lxc-execute-find-init: lxc-init had moved. Introduce a function in lxc-execute to go find it. Otherwise lxc-execute for any older releases will fail. * 0075-lxc-ls-bash: lxc-ls needs bash, not sh * add debian/lxc.apparmor.in so DEB_HOST_MULTIARCH can be expanded * 0076-fix-sprintfs: - check return values for all sprintfs and snprintfs which could overflow (LP: #988918) * 0077-execute-without-rootfs: let lxc-execute succeed with no rootfs (LP: #981955) -- Serge Hallyn <serge.hal...@ubuntu.com> Thu, 26 Apr 2012 15:18:35 -0500 ** Changed in: lxc (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/988918 Title: buffer overflows possible in liblxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/988918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs