[Bug 1114098] New: fedora 20: etcd broken on install, very out of date, and misconfigured.
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1114098
Bug ID: 1114098
Summary: fedora 20: etcd broken on install, very out of date,
and misconfigured.
Product: Fedora
Version: 20
Component: etcd
Assignee: lacypret(a)gmail.com
Reporter: bugs(a)jameskyle.org
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, lacypret(a)gmail.com,
lemenkov(a)gmail.com
Description of problem:
etcd service on fedora 20 only returns 404 page not found for all queries.
Version-Release number of selected component (if applicable):
Fedora 20, etcd 0.1.3
How reproducible:
100%
Steps to Reproduce:
1. yum install etcd
2. systemctl start etcd
3. curl http://127.0.0.1:4001/v2/keys/foo -d "Bar"
Actual results:
404 page not found
Expected results:
{"action":"set","node":{"key":"/message","value":"Hello","modifiedIndex":5,"createdIndex":5}}
Additional info:
The service was configured to use a systemd socket service, but (from the
systemd debs) "etcd doesn't have socket activation".
Even if I disabled the socket service and ran etcd 0.1.3 in the foreground with
defaults, the same behavior was manifest.
Installing the current 0.4.4 version of etcd produced the expected/desired
behavior.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 4 months
[Bug 1169151] New: docker run fails with 'finalize namespace error'
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1169151
Bug ID: 1169151
Summary: docker run fails with 'finalize namespace error'
Product: Fedora
Version: rawhide
Component: docker-io
Assignee: lsm5(a)mail2tor.com
Reporter: lsm5(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
hushan.jia(a)gmail.com, jchaloup(a)redhat.com,
jperrin(a)centos.org, lsm5(a)mail2tor.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com
Description of problem:
$ sudo docker run -it fedora bash
Unable to find image 'fedora' locally
fedora:latest: The image you are pulling has been verified
511136ea3c5a: Pull complete
782cf93a8f16: Pull complete
7d3f07f8de5f: Pull complete
Status: Downloaded newer image for fedora:latest
finalize namespace setup user setgid operation not supported2014/11/30 11:34:50
Error response from daemon: Cannot start container
99dd8c91dcb56e19153cf5d4b87f8fed7b5001526fe229d7933c0bf30dc8655f: finalize
namespace setup user setgid operation not supported
Version-Release number of selected component (if applicable): 1.3.2-2.fc22
How reproducible: always
Steps to Reproduce:
1. install docker
2. run aforementioned command
Additional info:
This error doesn't seem to occur with upstream commit 353ff40 on master branch
(1.3.2-dev)
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 4 months
[Bug 1167507] New: CVE-2014-6407 docker-io: docker: symbolic and hardlink issues leading to privilege escalation [fedora-all]
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1167507
Bug ID: 1167507
Summary: CVE-2014-6407 docker-io: docker: symbolic and hardlink
issues leading to privilege escalation [fedora-all]
Product: Fedora
Version: 20
Component: docker-io
Keywords: Security, SecurityTracking
Severity: low
Priority: low
Assignee: lsm5(a)fedoraproject.org
Reporter: mmcallis(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
hushan.jia(a)gmail.com, jchaloup(a)redhat.com,
jperrin(a)centos.org, lsm5(a)fedoraproject.org,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com
Blocks: 1167505 (CVE-2014-6407)
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time. If you need to fix the versions independent of each other,
you may clone this bug as appropriate.
[bug automatically created by: add-tracking-bugs]
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1167505
[Bug 1167505] CVE-2014-6407 docker: symbolic and hardlink issues leading to
privilege escalation
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 4 months
[Bug 1167505] New: CVE-2014-6407 docker: symbolic and hardlink issues leading to privilege escalation
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1167505
Bug ID: 1167505
Summary: CVE-2014-6407 docker: symbolic and hardlink issues
leading to privilege escalation
Product: Security Response
Component: vulnerability
Keywords: Security
Severity: low
Priority: low
Assignee: security-response-team(a)redhat.com
Reporter: mmcallis(a)redhat.com
CC: admiller(a)redhat.com, dwalsh(a)redhat.com,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
jchaloup(a)redhat.com, jperrin(a)centos.org,
lsm5(a)fedoraproject.org, mattdm(a)redhat.com,
mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io,
thrcka(a)redhat.com, vbatts(a)redhat.com
The following flaw has been fixed in Docker 1.3.2:
""
The Docker engine, up to and including version 1.3.1, was vulnerable to
extracting files to arbitrary paths on the host during ‘docker pull’ and
‘docker load’ operations. This was caused by symlink and hardlink
traversals present in Docker's image extraction. This vulnerability could
be leveraged to perform remote code execution and privilege escalation.
Docker 1.3.2 remedies this vulnerability. Additional checks have been added
to pkg/archive and image extraction is now performed in a chroot. No
remediation is available for older versions of Docker and users are advised
to upgrade.
""
Acknowledgements:
Red Hat would like to thank the Docker project for reporting these issues.
Upstream acknowledges Florian Weimer of Red Hat Product Security and
independent researcher Tõnis Tiigi as the original reporters.
Reference:
http://seclists.org/oss-sec/2014/q4/781
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 4 months
[Bug 1167506] New: CVE-2014-6408 docker: potential container escalation
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1167506
Bug ID: 1167506
Summary: CVE-2014-6408 docker: potential container escalation
Product: Security Response
Component: vulnerability
Keywords: Security
Severity: low
Priority: low
Assignee: security-response-team(a)redhat.com
Reporter: mmcallis(a)redhat.com
CC: admiller(a)redhat.com, dwalsh(a)redhat.com,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
jchaloup(a)redhat.com, jperrin(a)centos.org,
lsm5(a)fedoraproject.org, mattdm(a)redhat.com,
mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io,
thrcka(a)redhat.com, vbatts(a)redhat.com
The following flaw has been fixed in Docker 1.3.2:
""
Docker versions 1.3.0 through 1.3.1 allowed security options to be applied
to images, allowing images to modify the default run profile of containers
executing these images. This vulnerability could allow a malicious image
creator to loosen the restrictions applied to a container’s processes,
potentially facilitating a break-out.
Docker 1.3.2 remedies this vulnerability. Security options applied to
images are no longer consumed by the Docker engine and will be ignored.
Users are advised to upgrade.
""
Acknowledgements:
Red Hat would like to thank the Docker project for reporting this issue.
Reference:
http://seclists.org/oss-sec/2014/q4/781
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 4 months
[Bug 1167508] New: CVE-2014-6407 docker-io: docker: symbolic and hardlink issues leading to privilege escalation [epel-6]
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1167508
Bug ID: 1167508
Summary: CVE-2014-6407 docker-io: docker: symbolic and hardlink
issues leading to privilege escalation [epel-6]
Product: Fedora EPEL
Version: el6
Component: docker-io
Keywords: Security, SecurityTracking
Severity: low
Priority: low
Assignee: lsm5(a)fedoraproject.org
Reporter: mmcallis(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
hushan.jia(a)gmail.com, jchaloup(a)redhat.com,
jperrin(a)centos.org, lsm5(a)fedoraproject.org,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com
Blocks: 1167505 (CVE-2014-6407)
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora EPEL.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
epel-6 tracking bug for docker-io: see blocks bug list for full details of the
security issue(s).
This bug is never intended to be made public, please put any public notes
in the blocked bugs.
[bug automatically created by: add-tracking-bugs]
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1167505
[Bug 1167505] CVE-2014-6407 docker: symbolic and hardlink issues leading to
privilege escalation
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 4 months
[Bug 1167642] New: docker-io-1.3.2 is available
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1167642
Bug ID: 1167642
Summary: docker-io-1.3.2 is available
Product: Fedora
Version: rawhide
Component: docker-io
Keywords: FutureFeature, Triaged
Assignee: lsm5(a)fedoraproject.org
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
hushan.jia(a)gmail.com, jchaloup(a)redhat.com,
jperrin(a)centos.org, lsm5(a)fedoraproject.org,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com
Latest upstream release: 1.3.2
Current version/release in Fedora Rawhide: 1.3.1-2.fc22
URL: https://github.com/docker/docker/releases
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring Soon this service
will be implemented by a new system: https://release-monitoring.org/
It will require to manage monitored projects via a new web interface. Please
make yourself familiar with the new system to ease the transition.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 4 months
[Bug 1169035] New: Docker-io-1.3.2 needs device-mapper-libs-1.02.90 but in fact it is not in Fedora 20 repository
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1169035
Bug ID: 1169035
Summary: Docker-io-1.3.2 needs device-mapper-libs-1.02.90 but
in fact it is not in Fedora 20 repository
Product: Fedora
Version: 20
Component: docker-io
Assignee: lsm5(a)fedoraproject.org
Reporter: liangsuilong(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
hushan.jia(a)gmail.com, jchaloup(a)redhat.com,
jperrin(a)centos.org, lsm5(a)fedoraproject.org,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com
Description of problem:
Docker-io-1.3.2 needs device-mapper-libs-1.02.90 but in fact it is not in
Fedora 20 repository.
Version-Release number of selected component (if applicable):
docker-io-1.3.2-2.fc20.x86_64
How reproducible:
Just need to run yum update command.
Steps to Reproduce:
1. Enable update-testing repo.
2. Run yum update command.
Actual results:
[fedora@fedora-laptop edo_console]$ sudo yum update
[sudo] password for fedora:
Loaded plugins: langpacks, refresh-packagekit
Resolving Dependencies
--> Running transaction check
---> Package docker-io.x86_64 0:1.3.1-2.fc20 will be updated
---> Package docker-io.x86_64 0:1.3.2-2.fc20 will be an update
--> Processing Dependency: device-mapper-libs >= 1.02.90-1 for package:
docker-io-1.3.2-2.fc20.x86_64
---> Package sqlite.i686 0:3.8.7-1.fc20 will be updated
---> Package sqlite.x86_64 0:3.8.7-1.fc20 will be updated
---> Package sqlite.i686 0:3.8.7.2-1.fc20 will be an update
---> Package sqlite.x86_64 0:3.8.7.2-1.fc20 will be an update
--> Finished Dependency Resolution
Error: Package: docker-io-1.3.2-2.fc20.x86_64 (updates-testing)
Requires: device-mapper-libs >= 1.02.90-1
Installed: device-mapper-libs-1.02.85-1.fc20.x86_64 (@updates)
device-mapper-libs = 1.02.85-1.fc20
Available: device-mapper-libs-1.02.82-3.fc20.i686 (fedora)
device-mapper-libs = 1.02.82-3.fc20
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
In fact, the older docker-io package. docker-io-1.3.2-1.fc20.x86_64, has the
same problem in Fedora 20.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 4 months