summaryrefslogtreecommitdiffstats
path: root/usr.bin/uudecode
Commit message (Collapse)AuthorAgeFilesLines
* MFC r264400,r265836:ngie2014-12-311-1/+1
| | | | | | | | | | | | | | r264400: NO_MAN= has been deprecated in favor of MAN= for some time, go ahead and finish the job. ncurses is now the only Makefile in the tree that uses it since it wasn't a simple mechanical change, and will be addressed in a future commit. r265836: Remove last two NO_MAN= in the tree. In both of these cases, MAN= is what is needed.
* MFC various moves of tools/regressions/ tests to the new infrastructure.jmmv2014-04-277-1/+220
| | | | | | | | | | | | | | | | - r263220 Migrate tools/regression/sbin/ to the new tests layout. - r263222 Add Makefile missed in r263220. - r263226 Migrate tools/regression/{usr.bin/lastcomm,usr.sbin}/ to the new tests layout. - r263227 Migrate most of tools/regression/usr.bin/ to the new tests layout. - r263345 Expand tabs that sneaked in into spaces. - r263346 Migrate tools/regression/usr.bin/make/ to the new tests layout. - r263348 Add Makefiles missed in r263346. - r263351 Migrate tools/regression/usr.bin/pkill/ to the new tests layout. - r263388 Mark multi_test as requiring /usr/share/dict/words. - r263814 Fix path to the run.pl script to let these tests run. - r264742 Prevent building tests when bootstrapping make. This is 'make tinderbox' clean.
* Remove the advertising clause from UCB copyrighted files in usr.bin. Thisjoel2010-12-111-4/+0
| | | | | | | | | 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 encodededwin2010-10-181-5/+31
| | | | | | | | | | | | | | | | | | | | 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 <marka@isc.org> MFC after: 2 weeks
* Stylify of uudecode(1)edwin2010-10-181-29/+35
| | | | | | | Part of PR bin/124739. PR: bin/124739 Submitted by: Mark Andrews <marka@isc.org>
* Build usr.bin/ with WARNS=6 by default.ed2010-01-021-1/+0
| | | | Also add some missing $FreeBSD$ to keep svn happy.
* Start the dreaded NOFOO -> NO_FOO conversion.ru2004-12-211-1/+1
| | | | OK'ed by: core
* For variables that are only checked with defined(), don't provideru2004-10-241-1/+1
| | | | any fake value.
* Make GCC 3.3 happy with rcsid[], sccs[], and copyright[].obrien2003-05-031-2/+1
|
* The POSIXly-correct /dev/stdout handling added in rev 1.44 makesfanf2003-03-181-1/+1
| | | | | | | | | | 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 thanfanf2003-03-041-1/+1
| | | | the opposite. Does this pointy hat look good on me?
* Pull some common uu/b64 code out into shared functions. Move somefanf2003-02-271-36/+44
| | | | | | | | | | 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 thefanf2003-02-271-11/+36
| | | | | 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"fanf2003-02-271-2/+3
| | | | not a special file.
* Variables that come in in and out pairs should be named accordingly.fanf2002-11-011-68/+84
| | | | | | 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.
* Be much more paranoid about where uudecode writes its output, especiallyfanf2002-11-011-7/+36
| | | | | | | when the filename comes from the untrusted input. This is a work-around for careless people who don't routinely check the begin line of the file or run uudecode -i and instead report "vulnerabilities" to CERT. http://www.kb.cert.org/vuls/id/336083
* Instead of abusing stdin and stdout, use our own file pointers.fanf2002-11-011-14/+22
| | | | Check for errors when closing the output.
* Some uses of the variable n needed to be int, others needed to bemike2002-09-111-8/+8
| | | | size_t. Add a new variable to cope.
* Unbreak world by fixing 4 syntax errors and 1 wrong variable type.mike2002-09-111-5/+5
|
* Fix style bugs in macros.fanf2002-09-101-9/+6
|
* Tidy up the base64 code and relax the error handling.fanf2002-09-101-18/+28
|
* Style: Don't treat pointers as booleans.fanf2002-09-101-2/+2
|
* Fix tilde-expansion of the filename obtained from the "begin" line in -sfanf2002-09-101-95/+84
| | | | | | mode, and be more accurate about identifying begin lines so that spurious ones don't have to be manually edited out, and be more forgiving about errors so that -c mode is more useful.
* Replace a goto with continue.fanf2002-09-101-2/+1
|
* Remove register keyword.fanf2002-09-101-2/+2
|
* Style: space after return.fanf2002-09-101-15/+15
|
* Make the handling of -i neater.fanf2002-09-101-14/+10
|
* Only try to chmod the output if it's a regular file, rather thanfanf2002-09-101-4/+4
| | | | | | hard-coding /dev/stdout as a special case. Suggested by: jmallett
* Don't try (and fail) to fchmod /dev/stdout. Revert the manual pagefanf2002-09-031-0/+2
| | | | | | | | to suggest the portable alternative to -p. PR: 42356 Submitted by: Kimura Fuyuki <fuyuki@hadaly.org> MFC after: 1 week
* Remove spurious whitespacefanf2002-09-031-8/+6
|
* Synch usage() and manpage for b64encode/b64decode.jmallett2002-05-191-2/+5
| | | | Make uudecode's usage more like that of other programs.
* Add b64decode & b64encode as synonyms for uudecode and uuencode -m,jmallett2002-05-191-0/+1
| | | | | | respectively, for convenience when encoding or decoding base64 files. As requested by various users.
* Finish converting the rest of the function declaration and prototypesmike2002-05-121-10/+9
| | | | to ANSI C. Use new source ID scheme.
* unbreak build:alfred2002-05-111-3/+1
| | | | | K&R style main() makes gcc emit a warning about missing prototypes so switch to ANSI.
* Use fwrite(3) to write out the decoded information, as the b64 decoding stuffjmallett2002-04-201-1/+1
| | | | | | | | won't NUL terminate the string for us, and so we're liable to pick up trailing garbage, possibly tons of it. Pointed out by: obrien MFC after: 3 days
* base64_decode() was feeding \r and \n to the decoding function, and thatjmallett2002-04-201-0/+4
| | | | | | | was causing output to be corrupted. Pointed out by: obrien MFC after: 3 days
* Bump WARNS to 4.jmallett2002-04-201-0/+1
|
* remove __Pimp2002-03-221-4/+4
|
* Fix handling of filenames with spaces in them in the input file tojmallett2002-03-191-1/+1
| | | | | | | | | | uudecode(1), as this behaviour was explicitly added in revision 1.12 as the result of PR 2882. Remove space (' ') from the delimiter characters handed to strtok(3). Reviewed by: mike Approved by: mike Pointy hat to: me
* Make uudecode(1) use setmode(3) and getmode(3) instead of just blindlyjmallett2002-03-191-39/+50
| | | | | | | | | | | | | chmodding using an octal mode, as uudecode needs to handle symbolic modes as chmod and such do. Suggested by: Tim J. Robbins <tim@robbins.id.au> Also move meta-character (~ in this case) globbing to only if we are reading the filename from the encoded file, as otherwise it is the shell's job. Reviewed by: mike Approved by: mike
* Add base64 support to uuencode(1) and uudecode(1), as specified by SUSv3.jmallett2002-03-051-8/+41
| | | | | | | | Add `-o' option to uuencode(1) to pipe the uuencoded output to an arbitrary file, instead of just stdout. Reviewed by: -standards, mike Approved by: mike
* Un-deprecate the -p option. We now have two ways to output to stdout:mike2002-02-161-1/+0
| | | | | | `-o /dev/stdout' or `-p'. Requested by: grog, nectar
* Add -o option (POSIX.1-2001) to uudecode(1). Deprecate the -p optionmike2002-01-271-3/+26
| | | | | | | | (which allows one to redirect output to stdout); `-o /dev/stdout' is recommended instead. Submitted by: Joseph Mallett <jmallett@xMach.org> MFC after: 2 weeks
* WARNS=2 is to become the default, so remove it from here.markm2001-12-111-1/+0
|
* Style improvements recommended by Bruce as a follow up to somedwmalone2001-12-101-1/+1
| | | | | | | | of the recent WARNS commits. The idea is: 1) FreeBSD id tags should follow vendor tags. 2) Vendor tags should not be compiled (though copyrights probably should). 3) There should be no blank line between including cdefs and __FBSDIF.
* Warns cleanup. Add FreeBSD ID to Makefile.dwmalone2001-12-032-1/+3
|
* While I'm in here, remove an unused variable.sheldonh2000-03-301-1/+1
| | | | Submitted by: Nathan Ahlstrom <nrahlstr@winternet.com>
* Do not overwrite files when the -i option is specified!sheldonh2000-03-271-10/+14
| | | | | PR: 17476 Reported by: Jonathan Chen <jon@spock.org>
* $Id$ -> $FreeBSD$peter1999-08-281-1/+1
|
* Allow spaces in the filename to be decoded to.steve1998-05-251-2/+2
| | | | | PR: 4882 Submitted by: Slaven Rezic <eserte@cs.tu-berlin.de>
OpenPOWER on IntegriCloud