[Bug 1114816] CVE-2014-3499 docker-io: docker: systemd socket activation results in privilege escalation [epel-7]

https://bugzilla.redhat.com/show_bug.cgi?id=1114816 Lokesh Mandvekar changed: What|Removed |Added Status|NEW |CLOSED Resolution|---

[Bug 1114810] CVE-2014-3499 docker-io: docker: systemd socket activation results in privilege escalation [fedora-all]

https://bugzilla.redhat.com/show_bug.cgi?id=1114810 --- Comment #2 from Trevor Jay --- Vincent Danen wrote in a related bug: > The fix for this seems to be as simple as editing > /usr/lib/systemd/system/docker.socket and change the [Socket] section to: > > [Socket] > ListenStream=/var/run/dock

[Bug 1114811] CVE-2014-3499 docker-io: docker: systemd socket activation results in privilege escalation [epel-6]

https://bugzilla.redhat.com/show_bug.cgi?id=1114811 --- Comment #2 from Trevor Jay --- docker-io is already in Fed 20. Recommended fix is to simply pull from EPEL. -- You are receiving this mail because: You are on the CC list for the bug. ___ golan

[Bug 1114816] CVE-2014-3499 docker-io: docker: systemd socket activation results in privilege escalation [epel-7]

https://bugzilla.redhat.com/show_bug.cgi?id=1114816 --- Comment #2 from Trevor Jay --- docker-io is already in Fed 20. Recommended fix is to simply pull from EPEL. -- You are receiving this mail because: You are on the CC list for the bug. ___ golan

[Bug 1114816] New: CVE-2014-3499 docker-io: docker: systemd socket activation results in privilege escalation [epel-7]

https://bugzilla.redhat.com/show_bug.cgi?id=1114816 Bug ID: 1114816 Summary: CVE-2014-3499 docker-io: docker: systemd socket activation results in privilege escalation [epel-7] Product: Fedora EPEL Version: epel7 Component:

[Bug 1114816] CVE-2014-3499 docker-io: docker: systemd socket activation results in privilege escalation [epel-7]

https://bugzilla.redhat.com/show_bug.cgi?id=1114816 --- Comment #1 from Trevor Jay --- Use the following update submission link to create the Bodhi request for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get upd

[Bug 1114811] New: CVE-2014-3499 docker-io: docker: systemd socket activation results in privilege escalation [epel-6]

https://bugzilla.redhat.com/show_bug.cgi?id=1114811 Bug ID: 1114811 Summary: CVE-2014-3499 docker-io: docker: systemd socket activation results in privilege escalation [epel-6] Product: Fedora EPEL Version: el6 Component: do

[Bug 1114810] CVE-2014-3499 docker-io: docker: systemd socket activation results in privilege escalation [fedora-all]

https://bugzilla.redhat.com/show_bug.cgi?id=1114810 --- Comment #1 from Trevor Jay --- Use the following update submission link to create the Bodhi request for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get upd

[Bug 1114811] CVE-2014-3499 docker-io: docker: systemd socket activation results in privilege escalation [epel-6]

https://bugzilla.redhat.com/show_bug.cgi?id=1114811 --- Comment #1 from Trevor Jay --- Use the following update submission link to create the Bodhi request for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get upd

[Bug 1114810] New: CVE-2014-3499 docker-io: docker: systemd socket activation results in privilege escalation [fedora-all]

https://bugzilla.redhat.com/show_bug.cgi?id=1114810 Bug ID: 1114810 Summary: CVE-2014-3499 docker-io: docker: systemd socket activation results in privilege escalation [fedora-all] Product: Fedora Version: 20

[Bug 1087720] signal 27 (SIGPROF) not passed to container using --sig-proxy

https://bugzilla.redhat.com/show_bug.cgi?id=1087720 --- Comment #10 from Matthew Heon --- After further testing, I've managed to reproduce being unable to send signals 19, 18, and 27 to the container via --sig-proxy. This seems to be a Golang issue. I implemented a trivial signal-catching tes

[Bug 1096273] repetition of signal 21 with --sig-proxy and SIGSTOP of docker

https://bugzilla.redhat.com/show_bug.cgi?id=1096273 --- Comment #9 from Matthew Heon --- It appears I was confused about how to use SIGPROXY - apologies, your original report was valid. I can reproduce this on RHEL7 with -SIGSTOP and -SIGCONT, but not with -SIGSTOP and fg. This mainly has to

[Bug 1112748] Selinux prevents docker-io from updating /etc/passwd within a container

https://bugzilla.redhat.com/show_bug.cgi?id=1112748 Jim Perrin changed: What|Removed |Added CC||jper...@centos.org --- Comment #5 from J

[Bug 1101654] Permission denied when running Fedora images on Ubuntu

https://bugzilla.redhat.com/show_bug.cgi?id=1101654 Lokesh Mandvekar changed: What|Removed |Added CC||l...@switzerlandmail.ch As