src/usr.bin/uudecode, branch releng/9.2

Remove the advertising clause from UCB copyrighted files in usr.bin. This

2010-12-11T08:32:16+00:00

is in accordance with the information provided at
ftp://ftp.cs.berkeley.edu/pub/4bsd/README.Impt.License.Change

Also add $FreeBSD$ to a few files to keep svn happy.

Discussed with:	imp, rwatson

"b64decode -r" did not handle arbitary breaks in base64 encoded

2010-10-18T05:44:11+00:00

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 
MFC after:	2 weeks

Stylify of uudecode(1)

2010-10-18T03:59:55+00:00

Part of PR bin/124739.

PR:		bin/124739
Submitted by:	Mark Andrews

Build usr.bin/ with WARNS=6 by default.

2010-01-02T10:27:05+00:00

Also add some missing $FreeBSD$ to keep svn happy.

Start the dreaded NOFOO -> NO_FOO conversion.

2004-12-21T08:47:35+00:00

OK'ed by:	core

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

2004-10-24T15:33:08+00:00

any fake value.

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

2003-05-03T19:44:46+00:00

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

2003-03-18T14:19:26+00:00

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:05+00:00

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:18+00:00

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.)