Skip Menu |

This queue is for tickets about the Sendmail-PMilter CPAN distribution.

Report information
The Basics
Id: 23921
Status: resolved
Priority: 0/
Queue: Sendmail-PMilter

People
Owner: pause [...] jubileegroup.co.uk
Requestors: CDRAKE [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: 1.20_01



Subject: Feature request: remove buggy+unstable+dangerous import/requirement of Sendmail::Milter
Sendmail::Milter has some ghastly bugs, including enormous memory leaks, easily repeatable core-dumping, incorrect XS variable handling, and bodgey threads. Is is not suitable for installation on production environments, and could well pose root exploit threats. Since the only point of PMilter requiring this module is for the import of a dozen or so constants (that are hard-coded in sendmail, and will never change) - I would like to request that Sendmail::Milter be dropped as a requirement for PMilter (just grab the constants from sendmail, put them into your module, and remove all references to Sendmail::Milter).
On Wed Dec 13 22:11:52 2006, CDRAKE wrote: Show quoted text
> Sendmail::Milter has some ghastly bugs, including enormous memory > leaks, easily repeatable core-dumping, incorrect XS variable handling, > and bodgey threads. Is is not suitable for installation on production > environments, and could well pose root exploit threats. > > Since the only point of PMilter requiring this module is for the > import of a dozen or so constants (that are hard-coded in sendmail, > and will never change) - I would like to request that Sendmail::Milter > be dropped as a requirement for PMilter (just grab the constants from > sendmail, put them into your module, and remove all references to > Sendmail::Milter).
It actually requires either its own Sendmail::Milter or the /real/ Sendmail::Milter depending on whether the compatability interface was installed at make time. But you're right that this is dangerous, confusing and buggy so I'll probably factor out those constants into another module and make the Sendmail::Milter interface that's shipped with the module a real compatability skeleton that doesn't need to be used for anything else.
On Wed Dec 13 22:11:52 2006, CDRAKE wrote: Show quoted text
> Sendmail::Milter has some ghastly bugs, including enormous memory > leaks, easily repeatable core-dumping, incorrect XS variable handling, > and bodgey threads. Is is not suitable for installation on production > environments, and could well pose root exploit threats. > > Since the only point of PMilter requiring this module is for the > import of a dozen or so constants (that are hard-coded in sendmail, > and will never change) - I would like to request that Sendmail::Milter > be dropped as a requirement for PMilter (just grab the constants from > sendmail, put them into your module, and remove all references to > Sendmail::Milter).
(This is a copy/paste form letter) Hello bug submitter to Sendmail::PMilter. As you may or may not be aware Sendmail::Pmilter is effectively orphaned. You've opened an issue against it which the current maintainer (me) doesn't have the time/want to solve. See http://search.cpan.org/~avar/Sendmail-PMilter- 0.98/lib/Sendmail/PMilter.pm#Maintenance for more details. But worry not, you can help solve it yourself if you're interested by patching the module in Git and asking for co-maint permission to upload a new version of the module. Even though your fix may seem trivial to you keep in mind that I'd still need to apply / *TEST* / release it. The testing step would require installing Sendmail and I have no interest in doing so ever again. The reason I'm the maintainer in the first place is that I spotted & patched a problem that needed to be solved and then got maintainer permission because the module was orphaned at the time. It's now orphaned again so if you need fixes to it you're going to have top step up and overtake it.
Fixed in version 1.21, not yet released.