Not sure what the heck you all are recently taking about.
Most linux users of a ntfs partition are using to store files for use on any Os
or store files without any permission nonsense.
Those that actually place .exe files & want to then execute them from an Ubuntu
session would likely be using
> why it defaults to execute on when the in kernel driver does not.
Well, most users do not define the mapping of their user ids to Windows
ids, so the permissions cannot be stored to the device, and the
permissions have to be the same for all files and all users. If the
default was no-execute, th
Udisks specifying a default mask was removed intentionally, leaving the
default to the NTFS driver. ntfs-3g defaults to all executable. People
often do have executable files on their NTFS drives and want to be able
to execute them. This has gone back and forth a few times over the
years and with
Could somebody report that issue upstream on https://github.com
/storaged-project/udisks/issues ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728467
Title:
All files on ntfs partitions are marked
** Tags removed: zesty
** Tags added: bionic
** Tags removed: bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728467
Title:
All files on ntfs partitions are marked executable
To manage
Thank you very much for your offer, but I have messed up my system
trying to fix that and at this point I don't want to complicate matters
further (17.10 is quite buggy for me).
Would it be possible to submit your patch for official inclusion?
--
You received this bug notification because you ar
@ Matt -
here for my personal builds (16.04/18.04) i've altered source in this manner &
it does what's best for me -
-static const gchar *ntfs_defaults[] = { "uid=", "gid=", NULL };
+static const gchar *ntfs_defaults[] = { "uid=", "gid=", "fmask=0111", NULL };
If you'd like to try such builds u
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 lin
Please understand that this is severely affecting basic ubuntu use with ntfs
drives for basic users, while bug #453605 that is said to be the reason of the
misbehaviour has merely given more options to advanced users and was not
intended to mess up file handling in the way it presumably did.
If
If the intention of the changes was to make all files executable then
that was a poor decision (it does not appear that was the focus of the
whatsoever...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
The change was intentional. See bug #453605.
** Changed in: udisks2 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728467
Title:
All files on ntfs par
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: udisks2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728467
Title:
Al
** Tags removed: bionic
** Tags added: bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728467
Title:
All files on ntfs partitions are marked executable
To manage notifications about this
13 matches
Mail list logo
