dermund
Apprentice
Joined: 28 Aug 2007
Posts: 205
Location: Sprawl
|
 Posted: Mon Aug 16, 2010 3:06 pm Post subject: Truecrypt mount options |
 |
|
Hi,
This is a long post. This is my problem in short terms: Truecrypt does give mount.ntfs-3g incorrect mount options, resulting in a mounted volume with strange permissons set.
And here's the story:
1) If I mount the ntfs-3g volume with the truecrypt GUI and define no mount options in the settings then following is written to syslog:
| Code: | tail -f /var/log/messages
Aug 16 12:50:06 jugger ntfs-3g[17383]: Version 2010.3.6 external FUSE 28
Aug 16 12:50:06 jugger ntfs-3g[17383]: Mounted /dev/dm-0 (Read-Write, label "test1234", NTFS 3.1)
Aug 16 12:50:06 jugger ntfs-3g[17383]: Cmdline options: rw,uid=1000,gid=1000,umask=077
Aug 16 12:50:06 jugger ntfs-3g[17383]: Mount options: rw,silent,allow_other,nonempty,relatime,fsname=/dev/dm-0,blkdev,blksize=4096,default_permissions
Aug 16 12:50:06 jugger ntfs-3g[17383]: User mapping built, configuration type 1
|
Noticed that he passed options (uid,gid,umask) nevertheless!
The volume is then mounted with parameters that does not reflect the mentioned options. See:
| Code: |
drwxrwxrwx 1 myuser root 4,0K 15. Aug 20:55 truecrypt1
|
I guess from reading various other posts that this is due to "User mapping built, configuration type 1". If a user mapping is built, the fun is over! Why it is build, is the question.
2) If I pass mount options this time like "umask=022,uid=1000,gid=1000" in the GUI then following magic happens:
| Code: | Aug 16 12:51:41 jugger ntfs-3g[17465]: Version 2010.3.6 external FUSE 28
Aug 16 12:51:41 jugger ntfs-3g[17465]: Mounted /dev/dm-0 (Read-Write, label "test1234", NTFS 3.1)
Aug 16 12:51:41 jugger ntfs-3g[17465]: Cmdline options: rw,uid=1000,gid=1000,umask=077,umask=022,uid=1000,gid=1000
Aug 16 12:51:41 jugger ntfs-3g[17465]: Mount options: rw,silent,allow_other,nonempty,relatime,fsname=/dev/dm-0,blkdev,blksize=4096,default_permissions
Aug 16 12:51:41 jugger ntfs-3g[17465]: User mapping built, configuration type 1
|
Great! Now I have multiple double entries. User mapping in built and the volume is still mounted as above.
3) If I just let the GUI map the truecrypt device and not mount, and after this mount by hand with this:
| Code: | | mount -t ntfs-3g -o umask=0022,uid=1000,gid=1000 /dev/dm-0 /mnt/truecrypt1 |
I am happy again because following is written to syslog:
| Code: | Aug 16 12:48:00 jugger ntfs-3g[17276]: Version 2010.3.6 external FUSE 28
Aug 16 12:48:00 jugger ntfs-3g[17276]: Mounted /dev/dm-0 (Read-Write, label "test1234", NTFS 3.1)
Aug 16 12:48:00 jugger ntfs-3g[17276]: Cmdline options: rw,umask=0022,uid=1000,gid=1000
Aug 16 12:48:00 jugger ntfs-3g[17276]: Mount options: rw,silent,allow_other,nonempty,relatime,fsname=/dev/dm-0,blkdev,blksize=4096,default_permissions
Aug 16 12:48:00 jugger ntfs-3g[17276]: Global ownership and permissions enforced, configuration type 1
|
The volume is mounted as it should be with the options that I passed. This is due to the "Global ownership ..." line, I guess.
| Code: |
drwxr-xr-x 1 myuser myuser 4,0K 15. Aug 20:55 truecrypt1
|
This behaviour is annoying. Truecrypt GUI should not pass any stuff to ntfs-3g if the options are empty!
Maybe this is a bug in Truecrypt. Or is it human error?
Can someone try with mount options and post the relevant output of the syslog?
I use a local overlay with truecrypt 7.0.
Kind regards,
dermund |
|
Desktop Environments
