src-test2/usr.bin/uudecode, branch release/8.4.0

MFC of r214002, r214010

2010-11-03T10:10:34Z

- Stylify of uudecode(1) Part of PR bin/124739. - "b64decode -r" did not handle arbitary breaks in base64 encoded data. White space should be accepted anywhere in a base64 encoded stream, not just after every chunk (4 characters). Test-scenario: VmVsb2NpdHkgUmV3YXJkcw== and VmVsb2NpdHkgUmV3YXJkcw == should both produce "Velocity Rewards" PR: bin/124739 Submitted by: Mark Andrews

Start the dreaded NOFOO -> NO_FOO conversion.

2004-12-21T08:47:35Z

OK'ed by: core

For variables that are only checked with defined(), don't provide

2004-10-24T15:33:08Z

any fake value.

Make GCC 3.3 happy with rcsid[], sccs[], and copyright[].

2003-05-03T19:44:46Z

The POSIXly-correct /dev/stdout handling added in rev 1.44 makes

2003-03-18T14:19:26Z

careless users vulnerable to terminal control sequence attacks, since they expect uudecode to just drop (or overwrite) a file in the current directory. POSIX also says that the full pathname from the input should be used when writing a file, which we only do if the -s (shoot me in the foot) option is specified; therefore this revision means that you now need to use -s for standard /dev/stdout handling.

Don't complain about an early end-of-file in the -r case rather than

2003-03-04T21:22:05Z

the opposite. Does this pointy hat look good on me?

Pull some common uu/b64 code out into shared functions. Move some

2003-02-27T05:59:18Z

end-of-file checks out of the inner base64 loop, and remove the trailing whitespace stripper. The latter was added in rev 1.23 but the actual fix for the problem was in 1.24 -- b64_pton doesn't mind extra whitespace. (However there's a bogus comment in OpenSSH's uuencode.c that also mentions problems with trailing whitespace and b64_pton, but their real problem is the comment field in the key file.)

Add a relaxed mode for handling raw input which is missing the

2003-02-27T03:28:29Z

initial and possibly the final framing lines. This is particularly handy for dealing with broken files or fragments of MIME messages.

Be POSIXly correct in the handling of /dev/stdout -- it's a "magic cookie"

2003-02-27T02:24:01Z

not a special file.

Variables that come in in and out pairs should be named accordingly.

2002-11-01T02:08:51Z

Different code that processes the input in similar ways should be called in similar ways. File-local stuff should be static. Output errors should be checked for. Diffs sometimes have to be big.