Date: Tue, 25 Mar 1997 12:54:03 +0100 From: Wolfram Schneider <wosch@apfel.de> To: asami@vader.cs.berkeley.edu (Satoshi Asami) Cc: wosch@freebsd.org, current@freebsd.org, mita@jp.FreeBSD.org Subject: -current uudecode can't grok one of japanese/vfxdvi's distfiles Message-ID: <199703251154.MAA00909@campa.panke.de> In-Reply-To: <199703250726.XAA01567@silvia.HIP.Berkeley.EDU> References: <199703250726.XAA01567@silvia.HIP.Berkeley.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
Satoshi Asami writes: >uudecode: > input file: stdin > encoded file: xdvi-pl17+markpage+toc+printdvi+paper.patch.gz > character out of range: [33-96] >Do a boundary check for body characters. Characters less than 33 or >greater than 96 are out of range. If characters are out of range >uudecode print a error message and die. > >Is this check really necessary? Yes. All characters outside the range are garbage/bitrot and you get undefined results. >This file used to decode fine with >the old decoder. Besides, I can't figure out for the life of myself >which character it's barfing on. It use spaces (ASCII 32) in body. Spaces are bad because some mailers delete blank lines. Our uuencode never create spaces. See 'The UNIX-HATERS Handbook', page 82-83 I can add character 32 to the valid range for compatibility with old uuencode programs. -- Wolfram Schneider <wosch@apfel.de> http://www.apfel.de/~wosch/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703251154.MAA00909>