From owner-freebsd-security Tue Jul 28 19:00:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA12363 for freebsd-security-outgoing; Tue, 28 Jul 1998 19:00:34 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from lariat.lariat.org (ppp1000.lariat.org@[206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA12310 for ; Tue, 28 Jul 1998 19:00:10 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.8) id TAA26543; Tue, 28 Jul 1998 19:59:36 -0600 (MDT) Message-Id: <199807290159.TAA26543@lariat.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Tue, 28 Jul 1998 19:59:32 -0600 To: security@FreeBSD.ORG From: Brett Glass Subject: Any procmail experts here? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We have dozens of users who might get bit by the MIME filename buffer overflow bug described at http://www.sjmercury.com/business/microsoft/docs/security0728.htm and would like to try to use procmail to plug the hole (it seems to be the best tool for the job). However, I have no experience with procmail. Could someone help me write a procmail.rc that will eliminate the extra-long filenames, truncating them back to (say) 64 characters max? All that's required is to recognize the Content-type: .... filename="" header and make sure that is chopped if it's too long. This would be a fix for which thousands of sysadmins would be exceedinglyy grateful. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message