| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
the opposite. Does this pointy hat look good on me?
|
|
|
|
|
|
|
|
|
|
| |
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.)
|
|
|
|
|
| |
initial and possibly the final framing lines. This is particularly
handy for dealing with broken files or fragments of MIME messages.
|
|
|
|
| |
not a special file.
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Check for errors when closing the output.
|
|
|
|
| |
size_t. Add a new variable to cope.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
hard-coding /dev/stdout as a special case.
Suggested by: jmallett
|
|
|
|
|
|
|
|
| |
to suggest the portable alternative to -p.
PR: 42356
Submitted by: Kimura Fuyuki <fuyuki@hadaly.org>
MFC after: 1 week
|
| |
|
|
|
|
| |
Make uudecode's usage more like that of other programs.
|
|
|
|
| |
to ANSI C. Use new source ID scheme.
|
|
|
|
|
| |
K&R style main() makes gcc emit a warning about missing prototypes so
switch to ANSI.
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
was causing output to be corrupted.
Pointed out by: obrien
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 `-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
|
|
|
|
|
|
| |
`-o /dev/stdout' or `-p'.
Requested by: grog, nectar
|
|
|
|
|
|
|
|
| |
(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
|
| |
|
|
|
|
| |
Submitted by: Nathan Ahlstrom <nrahlstr@winternet.com>
|
|
|
|
|
| |
PR: 17476
Reported by: Jonathan Chen <jon@spock.org>
|
| |
|
|
|
|
|
| |
PR: 4882
Submitted by: Slaven Rezic <eserte@cs.tu-berlin.de>
|
|
|
|
|
|
|
|
| |
-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.
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
| |
posix standard on the topic.
|
|
|
|
|
|
| |
character as character 32 (space) instead character 64 (`).
See also 'The UNIX-HATERS Handbook', page 82-83.
|
| |
|
|
|
|
|
|
|
|
| |
"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.
|
|
|
|
|
| |
-p Decode file and write output to standard output.
-c Decode more than one uuencode'd file from file if possible.
|
| |
|
|
|
|
| |
produce such things.
|
|
|