From owner-freebsd-current Tue Mar 25 10:14:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA28297 for current-outgoing; Tue, 25 Mar 1997 10:14:23 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA28282; Tue, 25 Mar 1997 10:14:04 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <16874(4)>; Tue, 25 Mar 1997 10:13:27 PST Received: from localhost by crevenia.parc.xerox.com with SMTP id <177486>; Tue, 25 Mar 1997 10:13:10 -0800 To: asami@vader.cs.berkeley.edu (Satoshi Asami) cc: wosch@freebsd.org, current@freebsd.org, mita@jp.freebsd.org Subject: Re: -current uudecode can't grok one of japanese/vfxdvi's distfiles In-reply-to: Your message of "Mon, 24 Mar 97 23:26:17 PST." <199703250726.XAA01567@silvia.HIP.Berkeley.EDU> Date: Tue, 25 Mar 1997 10:13:01 PST From: Bill Fenner Message-Id: <97Mar25.101310pst.177486@crevenia.parc.xerox.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk asami@vader.cs.berkeley.edu (Satoshi Asami) wrote: >Do a boundary check for body characters. Characters less than 33 or >greater than 96 are out of range. This is not true. The original uuencode used characters in the range [32,95] . uuencode was modified to output 96 instead of 32 because 32 got munched on its way through too many mail gateways, but 32 is still a valid input character. Bill