In ubuntu 16.10/17.04/17.10, handling of ntfs drives has changed compared to 14.04.5. Now, all files on an ntfs drive are marked as executable.
This is bad for several reasons: - it just does not make any sense, data files are not executable, windows executables are usually not executable on linux - if there is a linux executable on the ntfs drive, security procedure on ext would be having to explicitly set the execute bit, why should it be "less" secure if the file resides on a different drive. - links (on ext, e.g. Desktop) to files residing on the ntfs drives are also marked executable. Error message: "The link ... is broken. Move it to Trash? This link cannot be used because its target ... doesn't exist." I first have to remove the execute bit from each and every link (which reapears instantly), only then they will be usable. All those links are invalid again after every reboot. Interestingly, if I remove the execute bit from a link AND open it using OpenWith... (not the standard application to open it) then ALL links to ntfs files become usable all of a sudden. - if I download a file to an ntfs drive and then try to open it using firefox download menu, I get a warning "Open executable file? ... is an executable file. Executable files can contain viruses or other malicious code that could harm your computer. Are you sure you want to execute ... ?" . This gives the false impression of a security risk! Please consider fixing this, if necessary by correcting the patch from https://bugs.launchpad.net/gvfs/+bug/453605 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1728467 Title: All files on ntfs partitions are marked executable Status in udisks2 package in Ubuntu: Confirmed Bug description: This did not happen in 14.04 but somewhere since then udisks2 sets any & all files on ntfs partitions as executable. Additionally if file is copied over to user's ext4 partion the bit remains set. Can't see why this would be intentional?? In 14.04 udisks2 - :static const gchar *ntfs_defaults[] = { "uid=", "gid=", "dmask=0077", "fmask=0177", NULL }; In 16.04, 17.04, 17.10,18.04 udisks2 - :static const gchar *ntfs_defaults[] = { "uid=", "gid=", NULL }; ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udisks2 2.1.7-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19~16.04.3-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity CustomUdevRuleFiles: 70-snap.core.rules Date: Sun Oct 29 21:20:19 2017 InstallationDate: Installed on 2017-09-16 (43 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 20217 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=b5ef3f68-8479-4c90-8c07-7fc4c165c5e9 ro quiet splash vt.handoff=7 SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1728467/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
