Bug 635559
Summary: | buffer overflow in star revisited | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Ondrej Vasik <ovasik> |
Component: | star | Assignee: | Ondrej Vasik <ovasik> |
Status: | CLOSED DUPLICATE | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 6.1 | CC: | azelinka, ovasik, robatino, wolfgang.pichler |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | 632384 | Environment: | |
Last Closed: | 2011-06-03 10:30:39 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: | |||
Bug Depends On: | 632384 | ||
Bug Blocks: |
Description
Ondrej Vasik
2010-09-20 07:31:01 UTC
This issue was proposed for RHEL 6.1 FasTrack but did not get resolved in time. It has been moved to RHEL 6.2 FasTrack. bug is not more reproducible since upgrade to fc14 i suppose eof-handling change in st-driver-code was improved so star was not disrupted by funny things bumped up from this special dlt-v4 device i use with star ... ... but i have no evidence for this : it is an assumption, not more i would suggest to close the bug if it occurs again i am prepared to reopen it again and we can start over again That bugzilla is about RHEL-6 - and is tracking the issue there. In RHEL-6 it was still not fixed because of the limited capacity for updates. Of course, in Fedora it is already fixed for a long time. Feel free to remove yourself from the CC list if you are not interested in watching the situation for RHEL-6. Could be considered as duplicate - as these two are closely related (same issue but on different places of source code) ... let's simplify it and mark it as dup. *** This bug has been marked as a duplicate of bug 611402 *** |