Bug 31561 - need to update to newer version
need to update to newer version
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: procmail (Show other bugs)
7.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-03-12 14:59 EST by Chris Ricker
Modified: 2007-04-18 12:32 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-03-12 15:30:28 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Chris Ricker 2001-03-12 14:59:31 EST
Currently, RH is building procmail 3.14 (even in the latest Rawhide).  This
really needs to be updated to procmail 3.15.1.  3.15.1 fixes a bug I'm
seeing where messages occasionally get bounced due to a race condition.  In
addition, the changelogs claim that 3.15.0 fixes attempts to exploit a
Linux kernel bug (I don't know the details of that, or if it's a problem,
or what).
Comment 1 Trond Eivind Glomsrxd 2001-03-12 15:22:14 EST
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.
Comment 2 Chris Ricker 2001-03-12 15:30:23 EST
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.
Comment 3 Trond Eivind Glomsrxd 2001-03-12 16:34:53 EST
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).

Note You need to log in before you can comment on or make changes to this bug.