Subject: pkg/13670: package nmh 1.0.4 mhbuild -check fails
To: None <gnats-bugs@gnats.netbsd.org>
From: None <mkb@mukappabeta.de>
List: netbsd-bugs
Date: 08/09/2001 19:24:08
>Number: 13670
>Category: pkg
>Synopsis: package nmh 1.0.4 mhbuild -check fails
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: pkg-manager
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Aug 09 12:30:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Matthias Buelow
>Release: 1.5
>Organization:
--mkb
>Environment:
System: NetBSD altair.mukappabeta.net 1.5 NetBSD 1.5 (ALTAIR) #3: Sat Jul 7 04:48:10 CEST 2001 root@altair.mukappabeta.net:/usr/src/sys/arch/i386/compile/ALTAIR i386
>Description:
[Notice: a copy of this report goes to the nmh-bugs reporting address.]
When mhbuild (from the mail/nmh package, version 1.0.4) is invoked
via the -check option (ought to add MD5 digests to MIME components),
it passes a NULL pointer to the open(2) system call, thus resulting
in an EFAULT returned from the open() and a rather meaningless message
from nmh, that it is "unable to open for reading":
1053 mhbuild CALL open(0,0,0x1b6)
1053 mhbuild RET open -1 errno 14 Bad address
mhbuild without -check works as expected.
>How-To-Repeat:
Add an entry for mhbuild to your $HOME/.mh_profile:
mhbuild: -check
Compose a message via comp, and add an exemplary MIME attachment directive:
#application/octet-stream [example: wc executable] /usr/bin/wc
then at the "What now?" prompt type "mime".
Alternatively, you could also invoke mhbuild -check directly on a
draft file, without having to modify .mh_profile.
>Fix:
Dunno yet.
>Release-Note:
>Audit-Trail:
>Unformatted: