[disks-admin] mounts NTFS with umask 0277, should be 0222

[Robin Haswell]

As the title says, disks-admin mounts NTFS partitions with umask 0277. This is confusing for users, when all other partitions are mounted with a umask that permits the user to read the disk. Either mount with -o umask=0222 by default, or provide a mesage explaining why you might not be able to read the disk and asking if you want to mount as "readable".

[Sebastien Bacher (seb128)]

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

[Colin Watson (cjwatson)]

If this is really about what disks-admin does to partitions that the installer hasn't already touched, then I don't think this is a duplicate of bug 8048. If it's about the /etc/fstab setup on fresh installations, then Sebastien is right.

[Robin Haswell (rob-digital-crocus)]

What? This is not a duplicate of bug #8048, I politely request that you re-read the bug report. Further more this bug needs to be fixed in order to resolve bug #23230, a much more serious security issue.

[Sebastien Bacher (seb128)]

Your bug description is not clear. Is the partition listed by fstab?

[Robin Haswell (rob-digital-crocus)]

No, I had to manually add the entries to /etc/fstab myself. disks-admin only mounted the filesystems, it didn't store the entries in fstab. I wasn't aware it was capable of that? This bug needs to be assigned back to gnome-system-tools, it is nothing to do with partman. Sorry for not making that clearer.

So for clarification:

1. My disks were not mounted when I installed Dapper
2. I was about to hackup fstab before I thought I would to see how GNOME was coming along on the filesystem management front.
3. I mounted an NTFS drive with it
4. I noticed I couldn't read it as a user, but the "browse" button allowed me to read it - disks-admin was running nautilus as root, so I filed a bug
5. I realised that in order to resolve that bug, disks-admin needs to mount NTFS partitions with -o umask=0222, which makes sense anyway

[Florian Boucault (fboucault)]

How does this bug relate to bugs #2198 and #55405 ?

[Sebastien Bacher (seb128)]

what option did you use for fstab? Does it work if you use "sudo mount ...." from the command line without specifying the umask?

[Daniel Holbach (dholbach)]

Your bug lacks information we would need to investigate further. We
are now going to close the bug - please reopen if you have more
information at hand.