Bug 735967
Summary: | gpg-agent segfaults via ..., pth_mutex_acquire, __pth_ring_append | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jim Meyering <meyering> |
Component: | gnupg2 | Assignee: | Rex Dieter <rdieter> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 16 | CC: | bcl, nalin, rdieter, tmraz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | gnupg2-2.0.18-1.fc16 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-09-30 19:28:19 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jim Meyering
2011-09-06 10:27:11 UTC
I've set priority to "HIGH". Anything that can make a security-sensitive tool like gpg segfault is important enough to fix ASAP. Can you please try this build: http://koji.fedoraproject.org/koji/buildinfo?buildID=264361 At least for me it fixed the crashing and the related code (estream.c) is touched in the upstream update. Thanks. With that, it no longer segfaults for me, either. gnupg2-2.0.18-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/gnupg2-2.0.18-1.fc16 Package gnupg2-2.0.18-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gnupg2-2.0.18-1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/gnupg2-2.0.18-1.fc16 then log in and leave karma (feedback). gnupg2-2.0.18-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |