Mailinglist Archive: opensuse (1461 mails)
| < Previous | Next > |
[opensuse] Crypt files using Yast2 partitioner
- From: Joop Beris <opensuse@xxxxxxxx>
- Date: Wed, 20 May 2009 15:13:46 +0200
- Message-id: <d73af006399913d6f0e7d2c290392c80@xxxxxxxx>
Hello listmates,
I'm trying to set up a crypt file, using the Yast2 partitioner.
What I want to do is the following:
- Create a crypt file in my home directory
- Make it mountable by my regular user account
- Not mount it automatically at boot
- Preferably make it expand automatically
So I start the Yast2 paritioner, go to Crypt Files and create a crypt file
in my home directory. I set the options in the appropriate steps steps of
the partitioner to make it user mountable and not to mount the crypt file
at system boot. I do not set a size or make a loop file, in the assumption
that this will create an auto-expanding crypt file. I choose a pass phrase
and proceed to commit the changes.
So far so good. The partitioner runs for a while, and then everything is
set.
However, the crypt file is mounted when the partitioner finishes. So, as
root, I unmount the crypt file. Then, I drop root privileges and try to
mount the crypt file as a regular user. To my surprise, I get this:
# mount -t ext3 /media/crypto/
mount: only root can do that
Now this is very odd. I had specified that the crypt file should be user
mountable. So I go back into the partitioner to edit the crypt file
settings. The settings for the crypt file seem empty when I open it. It
says "Do not format the partition" (which is understandable, because it is
already formatted) and it says "Do not mount partition". That is odd, since
I told it to mount at /media/crypto. Never mind, I enter that mount point
again and then click Fstab options. Here, my settings are also missing. I
had set it mountable by user and not to mount at system boot. Both options
are unchecked. I set them again, and click "Finish". It then tells me the
mount is already in use, which would be correct, since I already created
the fstab entry in the initial setup. The fstab line reads as follows:
/home/<user>/Crypto /media/crypto crypt
loop,user,noauto,acl,user_xattr 0 0
That looks okay to me.
Since the crypt file isn't working, I decide to delete it again. So in the
partitioner, I select the crypt file and click the delete button. Nothing
happens. The crypt file is still there, and also the entries in /etc/fstab
and /dev/disk/by-id and /dev/mapper remain.
So, am I doing something wrong, or is the Yast2 partitioner broken?
Regards,
Joop
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
I'm trying to set up a crypt file, using the Yast2 partitioner.
What I want to do is the following:
- Create a crypt file in my home directory
- Make it mountable by my regular user account
- Not mount it automatically at boot
- Preferably make it expand automatically
So I start the Yast2 paritioner, go to Crypt Files and create a crypt file
in my home directory. I set the options in the appropriate steps steps of
the partitioner to make it user mountable and not to mount the crypt file
at system boot. I do not set a size or make a loop file, in the assumption
that this will create an auto-expanding crypt file. I choose a pass phrase
and proceed to commit the changes.
So far so good. The partitioner runs for a while, and then everything is
set.
However, the crypt file is mounted when the partitioner finishes. So, as
root, I unmount the crypt file. Then, I drop root privileges and try to
mount the crypt file as a regular user. To my surprise, I get this:
# mount -t ext3 /media/crypto/
mount: only root can do that
Now this is very odd. I had specified that the crypt file should be user
mountable. So I go back into the partitioner to edit the crypt file
settings. The settings for the crypt file seem empty when I open it. It
says "Do not format the partition" (which is understandable, because it is
already formatted) and it says "Do not mount partition". That is odd, since
I told it to mount at /media/crypto. Never mind, I enter that mount point
again and then click Fstab options. Here, my settings are also missing. I
had set it mountable by user and not to mount at system boot. Both options
are unchecked. I set them again, and click "Finish". It then tells me the
mount is already in use, which would be correct, since I already created
the fstab entry in the initial setup. The fstab line reads as follows:
/home/<user>/Crypto /media/crypto crypt
loop,user,noauto,acl,user_xattr 0 0
That looks okay to me.
Since the crypt file isn't working, I decide to delete it again. So in the
partitioner, I select the crypt file and click the delete button. Nothing
happens. The crypt file is still there, and also the entries in /etc/fstab
and /dev/disk/by-id and /dev/mapper remain.
So, am I doing something wrong, or is the Yast2 partitioner broken?
Regards,
Joop
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
| < Previous | Next > |