cvs commit: ports/mail/metamail Makefile ports/mail/metamail/files

[nec...@freebsd.org]

nectar 2004/02/18 13:47:18 PST

FreeBSD ports repository

Modified files:
mail/metamail Makefile
mail/metamail/files patch-ae patch-af
Log:
Correct two format string vulnerabilities and two buffer overflows in
metamail (CVE names CAN-2004-0104 and CAN-2004-0104).

Submitted by: Ulf Härnhammar <Ulf.Harnh...@student.uu.se>

Revision Changes Path
1.21 +1 -0 ports/mail/metamail/Makefile
1.2 +20 -2 ports/mail/metamail/files/patch-ae
1.2 +58 -2 ports/mail/metamail/files/patch-af
_______________________________________________
cvs...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "cvs-all-u...@freebsd.org"

[nec...@freebsd.org]

On Wed, Feb 18, 2004 at 01:47:18PM -0800, Jacques A. Vidrine wrote:
> nectar 2004/02/18 13:47:18 PST
>
> FreeBSD ports repository
>
> Modified files:
> mail/metamail Makefile
> mail/metamail/files patch-ae patch-af
> Log:
> Correct two format string vulnerabilities and two buffer overflows in
> metamail (CVE names CAN-2004-0104 and CAN-2004-0104).
>
> Submitted by: Ulf Härnhammar <Ulf.Harnh...@student.uu.se>
>
> Revision Changes Path
> 1.21 +1 -0 ports/mail/metamail/Makefile
> 1.2 +20 -2 ports/mail/metamail/files/patch-ae
> 1.2 +58 -2 ports/mail/metamail/files/patch-af

You know, I'm almost certain these are not the only issues in this
port.

Please, will someone step forward to maintain this port and look for and
correct outstanding security issues therein? I can pass on some
information I have.

Otherwise (if a maintainer does *not* step forward), I will mark this
port FORBIDDEN. The only reason I don't do it now is because a few
other ports depend upon this one :-(

Cheers,
--
Jacques Vidrine / nec...@celabo.org / jvid...@verio.net / nec...@freebsd.org