markdashabout
October 25th, 2009, 05:07 PM
I have had an encrypted volume on my system for a while. Its encrypted with cryptmount, so that there is a entry in the file
/etc/cryptmount/cmtab
that looks like this:
hid3 {
dev=/home/mark/.hid3 dir=/home/mark/hid3
fstype=reiserfs fsoptions=defaults cipher=twofish
keyfile=/etc/cryptmount/hid3.key
keyhash=md5 keycipher=bf-cbc
flags=user,nofsck,nomkswap
}
After upgrade to 9.10 this works as expected, ie to gain access I type
cryptmount hid3
(passphrase)
and then
ls hid3
I can also do
echo a > hid3/a
An Icon appears on my desktop that shows a diskdrive, labelled hid3. If I click on this then I see all the files in hid3 as expected. However, after doing this, the file system has become read only.
echo a > hid3/a
bash: hid3/a: Read-only file system
Killing the window that now displays the contents of hid3 does not effect a restoration of write permissions. In fact the only thing that does seems to is unmounting and remounting the volume.
Has anyone come accross anything similar?
Is this a bug? Has anyone else reported it?
Can anyone advise a course of investigation?
11th November 09: Anybody? I mean how does a file system change to become read only without a change of permissions?
/etc/cryptmount/cmtab
that looks like this:
hid3 {
dev=/home/mark/.hid3 dir=/home/mark/hid3
fstype=reiserfs fsoptions=defaults cipher=twofish
keyfile=/etc/cryptmount/hid3.key
keyhash=md5 keycipher=bf-cbc
flags=user,nofsck,nomkswap
}
After upgrade to 9.10 this works as expected, ie to gain access I type
cryptmount hid3
(passphrase)
and then
ls hid3
I can also do
echo a > hid3/a
An Icon appears on my desktop that shows a diskdrive, labelled hid3. If I click on this then I see all the files in hid3 as expected. However, after doing this, the file system has become read only.
echo a > hid3/a
bash: hid3/a: Read-only file system
Killing the window that now displays the contents of hid3 does not effect a restoration of write permissions. In fact the only thing that does seems to is unmounting and remounting the volume.
Has anyone come accross anything similar?
Is this a bug? Has anyone else reported it?
Can anyone advise a course of investigation?
11th November 09: Anybody? I mean how does a file system change to become read only without a change of permissions?