summaryrefslogtreecommitdiffstats
path: root/usr.bin/uudecode
Commit message (Collapse)AuthorAgeFilesLines
* 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>
* Add two new options:wosch1998-01-251-9/+29
| | | | | | | | -i Do not overwrite files. -s Do not strip output pathname to base filename. By default uuencode deletes any prefix ending with the last slash '/' for security purpose.
* Many places in the code NULL is used in integer context, wherephk1997-09-181-2/+2
| | | | | | | | | plain 0 should be used. This happens to work because we #define NULL to 0, but is stylistically wrong and can cause problems for people trying to port bits of code to other environments. PR: 2752 Submitted by: Arne Henrik Juul <arnej@imf.unit.no>
* Use err(3).charnier1997-08-221-28/+22
|
* compare return value from getopt against -1 rather than EOF, per the finalimp1997-03-291-1/+1
| | | | posix standard on the topic.
* Be tolerant to old uuencode programs which encode the ASCII NULwosch1997-03-251-1/+1
| | | | | | character as character 32 (space) instead character 64 (`). See also 'The UNIX-HATERS Handbook', page 82-83.
* Treat 'end\0', 'end\n', 'end\r\n' as trailer line, see rev 1.2wosch1997-02-181-1/+3
|
* Better check for detecting header line. A header line must matchwosch1997-02-181-1/+32
| | | | | | | | "begin [0-7]* *". Now `begin with, ' is not a header line. 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.
* New options for uudecodewosch1996-10-211-5/+58
| | | | | -p Decode file and write output to standard output. -c Decode more than one uuencode'd file from file if possible.
* Oops, restore missing piece of previous commit.ache1996-04-251-1/+1
|
* Treat ^end<EOF> as valid terminator (like ^end\n), some encoders (f.e. Eudora)ache1996-04-251-1/+1
| | | | produce such things.
* BSD 4.4 Lite Usr.bin Sourcesrgrimes1994-05-272-0/+193
OpenPOWER on IntegriCloud