'uuencode' Question

[Tim Evans]

Why is it that 'uuencode' uses the invoking user's 'umask' for specifying
file permissions on the 'begin' line when you encode an existing file
but doesn't use it when you input to 'uuencode' from stdout?

For example:

uuencode foo foo > foobar

With my 'umask' of 022, this generates a 'begin' line like this:

begin 644 foo

If, however, I do:

cat foo | uuencode foo > foobar

The 'begin' line which results is:

begin 0 foo 

Naturally, in the second instance, decoding the file results in a file
with NO permissions of any kind.

If you reply via E-Mail, please do so to the address BELOW, not the
one in the headers to this posting.

THANKS.
-- 
cc:Mail		Tim K. Evans at ~OSS
UUCP 		...!{rutgers|ames|uunet}!mimsy!woodb!tkevans
INTERNET	tkevans%woodb at mimsy.umd.edu   PHONE:  (301) 965-3286
US MAIL		6401 Security Blvd, 2-Q-2 Operations, Baltimore, MD  21235