Bug 31561
Summary: | need to update to newer version | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Chris Ricker <chris.ricker> |
Component: | procmail | Assignee: | Trond Eivind Glomsrxd <teg> |
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-03-12 20:30:28 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
Chris Ricker
2001-03-12 19:59:31 UTC
That's not a problem, as the kernel has been fixed a long time ago. I don't want to upgrade at this late stage. I'll upgrade later. Like I said, I'm not so much concerned with the alleged security problem. I am, however, actually seeing the race-and-bounce fixed by 3.15.1. I've already had to upgrade two 7.0 boxes to 3.15.1 because of that and if you ship 7.1 with a known buggy procmail I'm going to have to do the same for all the 7.1 boxes I install. There are _no_ open bugs against it. And if we put in a new version, it wouldn't get that much testing - the chances of shipping something buggy would be higher. So I have a pretty high threshold of convincing right now... (and I and most others here use this every day without problems). |