Bug 1363726 - Files treated as executable
Summary: Files treated as executable
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: ntfs-3g
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-03 12:30 UTC by jeremy9856
Modified: 2017-07-27 06:51 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-07-27 06:51:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description jeremy9856 2016-08-03 12:30:51 UTC
Hello,

I'm on Fedora 24 and the files in my external USH HDD are always treated as executable. I thought it was a Nautilus bug but the Nautilus devs says it's an ntfs-3g problem (config ?) after I provided some gvfs-info and stat data as you can see in the bug report for Nautilus.

https://bugzilla.gnome.org/show_bug.cgi?id=769181

Is this a config problem that can "fixed" on ntfs-3g side ?

Thanks !

Comment 1 jeremy9856 2016-08-03 17:31:31 UTC
Of course I meant USB HDD drive and this drive is formatted in NTFS.

Here are more infos:

$ touch test.txt
$ stat test.txt 
  Fichier : 'test.txt'
   Taille : 0         	Blocs : 0          Blocs d'E/S : 4096   fichier vide
Périphérique : 841h/2113d	Inœud : 165731      Liens : 1
Accès : (0777/-rwxrwxrwx)  UID : ( 1000/  jeremy)   GID : ( 1000/  jeremy)
 Accès : 2016-08-03 19:22:29.386630100 +0200
Modif. : 2016-08-03 19:22:29.386630100 +0200
Changt : 2016-08-03 19:22:29.386630100 +0200
  Créé : -

I quote Ondrej Holy from Nautilus bug report https://bugzilla.gnome.org/show_bug.cgi?id=769181#c3

> I am conviced that there isn't any problem with the files on NTFS, stat shows executable bit, gvfs-info shows can-execute. You can modify umask/fmask/dmask to not mark them as executable, see man ntfs-3g

There is maybe a setting of ntfs-3g, that we could make the default, to not set every files executable ?

Comment 2 Jean-Pierre André 2016-08-08 07:43:09 UTC
By default, ntfs-3g creates files as owned by root with all permissions granted to anybody. Nevertheless the files may be set to appear as owned by some user by using the options uid= and gid=. In the reported example the options uid=1000 and gid=1000 were apparently set.

Similarly the options fmask= and dmask= may be used to make files to appear with permission restrictions. Setting fmask=0133 will make files to appear as non-executable.

These options (uid, gid, fmask, dmask) apply to all files, whether created by ntfs-3g or by Windows. They only act on how the files appear on Linux, the files created by ntfs-3g are still recorded to the device (and seen by Windows) as owned by root with all permissions granted.

If you want normal Linux-type ownership and permission for each individual file, you have to use the "permissions" option and define the user mapping. See http://jp-andre.pagesperso-orange.fr/permissions.html

Comment 3 jeremy9856 2016-08-08 08:19:24 UTC
Thank you Jean-Pierre but that's not exactly what I want. I, and I think this goes for almost everyone, simply want the files on NTFS partition not be treated as executable by default. Right now each time you double click on a text file on a NTFS partition you are ask if you want to launch it (with executable file text option in Nautilus set to "ask what to do").

There is maybe something to tweak in Fedora to have this behaviour out of the box ?

Comment 4 Fedora End Of Life 2017-07-25 22:14:06 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 5 jeremy9856 2017-07-27 06:51:18 UTC
Doesn't seem to be a bug.


Note You need to log in before you can comment on or make changes to this bug.