Attachment 7176 Details for Bug 16277 – Test example using cryptmount-setup

Test example using cryptmount-setup

cryptmount.test.txt (text/plain), 4.09 KB, created by Dave Hodgins on 2015-10-30 00:44:48 CET

(hide)

Description:

Filename:

MIME Type:

Creator: Dave Hodgins

Created: 2015-10-30 00:44:48 CET

Size: 4.09 KB

patch

obsolete

># cryptmount-setup            
>
>------------------------------
>cryptmount setup script
>
>This program will allow you to setup a secure filing-system that will 
>be managed by "cryptmount". You will be able to select basic features 
>such as the location and size of the filesystem - if you want more 
>advanced features, you should consult the cryptmount manual page.
>
>cryptmount version 5.0, (C)Copyright 2007-2014 RW Penney
>cryptmount comes with ABSOLUTELY NO WARRANTY.
>This is free software, and you are welcome to redistribute it under 
>certain conditions - see the file 'COPYING' in the source directory.
>
>------------------------------
>Each cryptmount filesystem is identifed by a short name which is used 
>when mounting or configuring that filesystem. This name should be a 
>single word (without spaces), such as "opaque".
>The following target names have already been used:    (NONE)
>
>  Please enter a target name for your filesystem
>  [opaque]: crypttest
>
>
>The crypttest filesystem can be configured to be owned by a nominated 
>user, who will be able to create top-level files & directories 
>without needing to involve the superuser.
>
>  Which user should own the filesystem (leave blank for "root")
>  []: dave
>
>
>In order to access the crypttest filesystem, it must be mounted on 
>top of an empty directory.
>
>  Please specify where "crypttest" should be mounted
>  [/home/dave/crypt]: 
>
>
>The maximum available size of your filesystem needs to be chosen so 
>that enough space can be reserved on your disk.
>
>  Enter the filesystem size (in MB)
>  [64]: 
>
>
>The actual encrypted filesystem will be stored in a special file, 
>which needs to be large enough to contain your entire encrypted 
>filesystem.
>
>  Enter a filename for your encrypted container
>  [/home/dave/crypto.fs]:          
>
>
>Access to your encrypted filesystem is protected by a key that is 
>kept in a separate small file. The key is locked by a password that 
>you must enter whenever you mount the filesystem.
>
>  Enter a location for the keyfile
>  [/etc/cryptmount/crypttest.key]: 
>
>------------------------------
>Your filing system is now ready to be built - this will involve:
> - Creating the directory "/home/dave/crypt"
> - Creating a 64MB file, "/home/dave/crypto.fs"
> - Adding an extra entry ("crypttest") in /etc/cryptmount/cmtab
> - Creating a key-file ("/etc/cryptmount/crypttest.key")
> - Creating an ext3 filingsystem on "/home/dave/crypto.fs"
>If you do not wish to proceed, no changes will be made to your system.
>
>  Please confirm that you want to proceed (enter "yes")
>  [no]: yes
>Making mount-point (/home/dave/crypt)... done
>Creating filesystem container (/home/dave/crypto.fs)... done
>Taking backup of cryptmount master config-file (/etc/cryptmount/cmtab.bckp-setup)... done
>Generating filesystem access key (/etc/cryptmount/crypttest.key)...
>Generating random key; please be patient...
>Enter new password for target "crypttest": 
>Confirm password: 
>Formatting encrypted filesystem...
>Enter password for target "crypttest": 
>
>------------------------------
>Your new encrypted filesystem is now ready for use - to access, try:
>    cryptmount crypttest
>    cd /home/dave/crypt
>After you have finished using the filesystem, try:
>    cd
>    cryptmount --unmount crypttest
>
>Please take great care NOT to delete or damage your keyfile 
>("/etc/cryptmount/crypttest.key"). Without that file, and the 
>associated password, it will be virtually impossible to access your 
>encrypted filesystem. You may want to keep a separate backup copy of 
>the keyfile.
>
>[dave@x3 ~]$ cryptmount --unmount crypttest
>[dave@x3 ~]$ cryptmount crypttest
>Enter password for target "crypttest": 
>e2fsck 1.42.12 (29-Aug-2014)
>/dev/mapper/crypttest: clean, 12/16384 files, 7478/65536 blocks
>[dave@x3 ~]$ cd crypt
>[dave@x3 crypt]$ echo test>test
>[dave@x3 crypt]$ cd
>[dave@x3 ~]$ df|grep crypt
>/dev/mapper/crypttest   58M  1.3M   54M   3% /home/dave/crypt
>[dave@x3 ~]$ cryptmount --unmount crypttest
>[dave@x3 ~]$ cryptmount crypttest
>Enter password for target "crypttest": 
>e2fsck 1.42.12 (29-Aug-2014)
>/dev/mapper/crypttest: clean, 12/16384 files, 7478/65536 blocks
>[dave@x3 ~]$ cat crypt/test 
>test
>[dave@x3 ~]$ cryptmount --unmount crypttest
>
>

# cryptmount-setup            

------------------------------
cryptmount setup script

This program will allow you to setup a secure filing-system that will 
be managed by "cryptmount". You will be able to select basic features 
such as the location and size of the filesystem - if you want more 
advanced features, you should consult the cryptmount manual page.

cryptmount version 5.0, (C)Copyright 2007-2014 RW Penney
cryptmount comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it under 
certain conditions - see the file 'COPYING' in the source directory.

------------------------------
Each cryptmount filesystem is identifed by a short name which is used 
when mounting or configuring that filesystem. This name should be a 
single word (without spaces), such as "opaque".
The following target names have already been used:    (NONE)

  Please enter a target name for your filesystem
  [opaque]: crypttest


The crypttest filesystem can be configured to be owned by a nominated 
user, who will be able to create top-level files & directories 
without needing to involve the superuser.

  Which user should own the filesystem (leave blank for "root")
  []: dave


In order to access the crypttest filesystem, it must be mounted on 
top of an empty directory.

  Please specify where "crypttest" should be mounted
  [/home/dave/crypt]: 


The maximum available size of your filesystem needs to be chosen so 
that enough space can be reserved on your disk.

  Enter the filesystem size (in MB)
  [64]: 


The actual encrypted filesystem will be stored in a special file, 
which needs to be large enough to contain your entire encrypted 
filesystem.

  Enter a filename for your encrypted container
  [/home/dave/crypto.fs]:          


Access to your encrypted filesystem is protected by a key that is 
kept in a separate small file. The key is locked by a password that 
you must enter whenever you mount the filesystem.

  Enter a location for the keyfile
  [/etc/cryptmount/crypttest.key]: 

------------------------------
Your filing system is now ready to be built - this will involve:
 - Creating the directory "/home/dave/crypt"
 - Creating a 64MB file, "/home/dave/crypto.fs"
 - Adding an extra entry ("crypttest") in /etc/cryptmount/cmtab
 - Creating a key-file ("/etc/cryptmount/crypttest.key")
 - Creating an ext3 filingsystem on "/home/dave/crypto.fs"
If you do not wish to proceed, no changes will be made to your system.

  Please confirm that you want to proceed (enter "yes")
  [no]: yes
Making mount-point (/home/dave/crypt)... done
Creating filesystem container (/home/dave/crypto.fs)... done
Taking backup of cryptmount master config-file (/etc/cryptmount/cmtab.bckp-setup)... done
Generating filesystem access key (/etc/cryptmount/crypttest.key)...
Generating random key; please be patient...
Enter new password for target "crypttest": 
Confirm password: 
Formatting encrypted filesystem...
Enter password for target "crypttest": 

------------------------------
Your new encrypted filesystem is now ready for use - to access, try:
    cryptmount crypttest
    cd /home/dave/crypt
After you have finished using the filesystem, try:
    cd
    cryptmount --unmount crypttest

Please take great care NOT to delete or damage your keyfile 
("/etc/cryptmount/crypttest.key"). Without that file, and the 
associated password, it will be virtually impossible to access your 
encrypted filesystem. You may want to keep a separate backup copy of 
the keyfile.

[dave@x3 ~]$ cryptmount --unmount crypttest
[dave@x3 ~]$ cryptmount crypttest
Enter password for target "crypttest": 
e2fsck 1.42.12 (29-Aug-2014)
/dev/mapper/crypttest: clean, 12/16384 files, 7478/65536 blocks
[dave@x3 ~]$ cd crypt
[dave@x3 crypt]$ echo test>test
[dave@x3 crypt]$ cd
[dave@x3 ~]$ df|grep crypt
/dev/mapper/crypttest   58M  1.3M   54M   3% /home/dave/crypt
[dave@x3 ~]$ cryptmount --unmount crypttest
[dave@x3 ~]$ cryptmount crypttest
Enter password for target "crypttest": 
e2fsck 1.42.12 (29-Aug-2014)
/dev/mapper/crypttest: clean, 12/16384 files, 7478/65536 blocks
[dave@x3 ~]$ cat crypt/test 
test
[dave@x3 ~]$ cryptmount --unmount crypttest

Actions: View

Attachments on bug 16277: 7114 | 7176