New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
© doesn't copy the file attributes in Rakudo #3680
Comments
From @masak<lizmat> $ ls -ls big* |
From 1parrota@gmail.comBeing really pedantic, the files have different "permissions". I'm "Umask" is what is applied to the default permissions, to set the Not replicating the original file permissions on a copy would be a I'm sure I'm teaching the choir "Our Father, &c." with this, but just On 2/11/15, Carl Mäsak <perl6-bugs-followup@perl.org> wrote:
|
The RT System itself - Status changed from 'new' to 'open' |
From @pmichaudOn Wed, Feb 11, 2015 at 04:21:32PM -0500, Parrot Raiser wrote:
I think this is overstating things a fair bit. A file that is root-read-only would only be readable by root, not "anybody". Assuming a non-root person has read permissions to a file that is "root-read-only" (whatever that means), there are plenty of ways to create a modifiable copy of that file without using ©. So © itself isn't the source (or fix) of the security hole. Ultimately I agree that the original file permissions should come into play, however. I suspect that © should create the new copy with the existing file's permissions as modified by the current umask. Pm |
This problem goes down to the libuv library that's used. Also, it should probably mention file attributes, not "umask", which is a different thing. |
Migrated from rt.perl.org#123800 (status was 'open')
Searchable as RT123800$
The text was updated successfully, but these errors were encountered: