If I compare your file listing with my own, I see that the ownership of the vault.fs file is different. You have to manually set the ownership to root. The command for this is:

 chown root:root vault.fs 

Hope this helps.

Cheers,
Ed

i have the same problem. When I mount /dev/mapper/vault at the mountpoint and start the command ls-l I get this.
drwsrwsr-x 4 www-data www-data 4096 Oct 11 10:52 PUBLIC
drwsrwsr-x 11 www-data www-data 4096 Oct 11 14:20 **
drwsrwsr-x 3 root root 1024 Oct 11 14:23 VAULT
drwsrwsr-x 2 www-data www-data 16384 Apr 10 2008 lost+found
-rw-rr 1 www-data www-data 1000000000 Oct 11 10:34 vault.fs
I think that there is something wrong. So please help me. I used the command chmod 6775 on the folder but it doesnt work.

Rippchen

I had to set the permissions of VAULT manually and include the SETGID explicitly. Using the webinterface of the MyBookWorld didn't do this. Don't know why it didn't do it, but I do know that my MyBookWorld is a rather early one.

Thank you very much for you help Andy.

I can write to, read from, modify files from Windows. Note that my /shares/internal/vault.fs file and VAULT directory has the following attributes:

-rw-rr 1 www-data www-data 8000000000 Jun 16 01:27 vault.fs
and
drwxrws—- 4 www-data www-data 4096 Jul 25 20:39 VAULT

Check that your files have similar ownership and attributes.

Andy

Accessing it via Windows is exactly the plan, but unfortunately it still gives the same error after I'd started from scratch again.

However, your explicit mentioning of Windows gave me the idea to try to copy a file on the MyBookWorld itself into the vault. And that works fine and from a Windows client I can see the copied file. I cannot rename it or delete it, but I can read it. Isn't this as simple as setting the access bits of the vault itself (on top of the access right that are granted via the Webinterface of the MyBook)?

What I don't understand is your remark about the SETGID bit. I looked it up, but as a Unix nood I could do much with what I found. Maybe that's something I have to do explicitly.

Sorry if I tire you with this noob-Q's :-)

Ed

Haven't been to this site for a while.

You probably left out some steps such as (Assuming you want to share this with Windows users):

Using MyBook's web interface, create a new folder call VAULT and assign access rights to users to access it.
This is the same procedure that you use to share folders to Windows users. If you create this directory using the web interface, it will set the permission correctly (including the SETGID bit). Once you mounted the device:
mount /dev/mapper/vault /shares/internal/VAULT
You should be able to read/write from Windows clients.

Is that what you are trying to do?

Andy

Hope this is an easy nut to crack :-)

Ed

Haven't tried it yet, but thanks in advance for your reply. I think I should be able to get it working now.

Cheers,
Ed

dd if=/dev/zero of=/shares/internal/vault.fs bs=1MB count=8000

This command creates an 8GByte file for the container. This takes under 5 minutes. You could use /dev/urandom instead of /dev/zero, but using /dev/uramdom will take around 1 hour per GBytes

Using MyBook's web interface, create a new folder call VAULT and assign access rights to users to access it.

Then create a shell script in /etc/init.d/valut.sh

 #!/bin/sh # # vault - to start or stop encrypted container # DEV=/dev/loop0 DMDEVNAME=vault DMDEV=/dev/mapper/$DMDEVNAME FILE=/shares/internal/vault.fs start() { if [ `df | grep $DMDEVNAME | wc -l` -eq 0 ]@@ then read key1 read key2 losetup $DEV $FILE echo 0 `ls -s $FILE | awk '{ print $1; }' ` ox-crypt $key1 $key2 0 $DEV 0 |/usr/sbin/dmsetup create $DMDEVNAME #mount $DMDEV /shares/internal/VAULT fi } stop() { if [ `df | grep $DMDEVNAME | wc -l` -ne 0 ] then umount $DMDEV /usr/sbin/dmsetup remove $DMDEV losetup -d $DEV fi } restart() { stop start } case "$1" in start) start ;; stop) stop ;; restart|reload) restart ;; *) echo $"Usage: $0 {start|stop|restart}" exit 1 esac exit $? 

Run the script: /etc/init.d/vault.sh start

This will ask for 2 32-digit keys from the command line (one line per key, no prompt)

After this, execut the command:
mkfs.ext3 -m 1 /dev/mapper/vault
mount /dev/mapper/vault /shares/internal/VAULT

This will mount the encrypted container and you can access it from Windows as a shared drive.

Edit the valut.sh you created and uncomment the line
#mount $DMDEV /shares/internal/VAULT

ie, remove the #

Before you shutdown MyBook, execute
/etc/init.d/vault.sh stop

The every time you power on, run the command /etc/init.d/vault.sh start
and enter the keys and shut down using /etc/init.d/vault.sh stop
If you want to retrieve the keys automatically on boot, check out the original encrypted drive post.

Note that if the encrypted file system is not mounted, you will see no files in the VAULT folder.

Andy

Thanks in advance.

/Ed

I do not want to encrypt the whole filesystem, thus is there a way to mount a hardware-encrypted container (file) as for example /shares/encrypted?

- Martin