Cheers Pedro, I'm in the works of hopefully narrowing the bug down a bit, so some updating in the upstream description might be required when done.
** Description changed: Binary package hint: nautilus TEST CASE: + 1. Create a symlink inside ~/ linking to either ~ or a directory within ~ 1. Launch nautilus - 2. Copy user directory to other location (e.g. /tmp) - 3. Skip "special files" which cannot be copied (nautilus pop-up dialogues) - 4. Check permissions of user's folder + 2. Copy directory ~ to other location (e.g. /tmp) + 4. Check permissions of the symlinked folder (the source, not the copy) - Result: user directory permissions is changed to 777 (drwxrwxrwx user:user) - Expected behaviour: user directory permissions should be unchanged (755, drwxr-xr-x user:user) - (To revert, simply use "chmod 755 ~") + Result: source ~ or folder permissions is changed to 777 (drwxrwxrwx user:user) + Expected behaviour: permissions should be unchanged (755, drwxr-xr-x user:user) + (To revert, simply use "chmod 755 foldername") Another side-effect of this is that on startup, gnome(?) gives an error about the .drmc file and permissions (although it does only complain at that file not being 644 [which it IS]) I'm flagging this as a security vulnerability since this allows unwanted write access to user's directory. ** Summary changed: - Permissions on user home directory (source) set to 777 after copying it via nautilus + Permission of source folder in ~ set to 777 if symlinked and copied via nautilus -- Permission of source folder in ~ set to 777 if symlinked and copied via nautilus https://bugs.launchpad.net/bugs/418135 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
