uuencode does not correctly encode file permissions when reading from stdin

[AlainKnaff]

When reading from stdin, uuencode does not correclty encode file permissions, but always assumes 644:

To reproduce:

> touch x
> chmod 755 x
> uuencode x <x
begin 644 x
`
end

[Serge Hallyn (serge-hallyn)]

Still the case today.

[Jon Grimm (jgrimm)]

I'm not sure this is actually a bug, but working as designed.

As being used one is specifying that input-file is coming off of stdin, so it uses hardcoded permissions (since it doesn't have anything else to really go on). Also not that when you are saying 'uuencode x' you 'x' is simple the output-name that will be put into the uuencode header, not the actual out-put filename, so it can be derived from that argument either.

So instead specifiy an input file if you want permissions to be derived from the actual input file:

jgrimm@jgrimm-ThinkPad-X250:~/tmp$ touch x
jgrimm@jgrimm-ThinkPad-X250:~/tmp$ chmod 755 x
jgrimm@jgrimm-ThinkPad-X250:~/tmp$ uuencode x x
begin 755 x
`
end