Tony Finch 55d8d447bf The POSIXly-correct /dev/stdout handling added in rev 1.44 makes ... 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.		2003-03-18 14:19:26 +00:00
..
Makefile	Add b64decode & b64encode as synonyms for uudecode and uuencode -m,	2002-05-19 11:17:17 +00:00
uudecode.c	The POSIXly-correct /dev/stdout handling added in rev 1.44 makes	2003-03-18 14:19:26 +00:00