Thu 02 of Sep, 2010 [15:27 UTC]
cryptsetup
|
Cryptsetup Info
|
|
Português Brasileiro |
We are an organized group of writers who specialize in producing custom academic papers of the highest quality. We also provide many other services including editing, review and translation. Our aim is to become the best, most trusted and preferred site for those who seek excellent academic papers. We provide our clients with ability to fulfill their writing needs with a standard that is unmatched.
cryptsetup 0.1 requires libgcrypt 1.1.x and libdevmapper
Don't forget to call scripts/devmap_mknod.sh (only once) in the device-mapper package to create the /dev/mapper/control device node if you don't use devfs or udev.
If you are interested in helping to develop cryptsetup contact Christophe about getting write access to his cvs server.
Logo Design
V0.1 Syntax
Syntax: /usr/local/sbin/cryptsetup <OPTIONS> <action> <name> <device>
<OPTIONS>:
-c <cipher> (see /proc/crypto)
-h {plain/<hash>} (see hashalot, WARNING: use ripemd160 instead of rmd160)
-y (verifies the passphrase by asking for it twice)
-d <file> (read key from file
e.g. /dev/urandom; useful for swap devices.
If set, the parameters -h and -y will be ignored)
-s <keysize> (in bits) (WARNING: in bytes for cryptsetup.sh)
-b <size> (in sectors)
-o <offset> (in sectors)
-p <skipped> (in sectors)
<action> is one of:
create - create device
remove - remove device
reload - modify active device
resize - resize active device
status - show device status
<name> is the device to create under /dev/mapper/
<device> is the encrypted device
When creating a device the program will ask for the a passphrase. The passphrase will then be hashed using the hashalot program and be used as key.
Alternatively a passphrase can be piped through stdin.
The hashing can be turned off with -h plain.
The defaults are aes with a 256 bit key, hashed using ripemd160.
Don't forget: cryptsetup only creates a mapping. If you call cryptsetup again after a reboot and supply the same passphrase you will be able to mount your filesystem you created before.
v0.1 - First Release
v0.1 - Can't mount files directly, use losetup first.
v0.1 - Can't mount read-only devices (CD/DVD-ROM's) use losetup first.
The latest version of cryptsetup is available by CVS. There is a web frontend to the CVS version here.
To check out the latest version from CVS do the following (keyboard input in bold):
^alex@berbara:~$ cvs -d:pserver:cvs@cvs.saout.de:/cvsroot/saout login
Logging in to :pserver:cvs@cvs.saout.de:2401/cvsroot/saout
CVS password: cvs
alex@berbara:~$ cvs -z3 -d:pserver:cvs@cvs.saout.de:/cvsroot/saout co cryptsetup
cvs server: warning: NULL value for key `All' at line 1 of `/cvsroot/saout/CVSROOT/modules'
cvs checkout: warning: NULL value for key `All' at line 1 of `/cvsroot/saout/CVSROOT/modules'
cvs checkout: Updating cryptsetup
U cryptsetup/AUTHORS
U cryptsetup/ChangeLog
U cryptsetup/Makefile.am
< SNIPP >
U cryptsetup/src/cryptsetup.c
U cryptsetup/src/cryptsetup.h
alex@berbara:~$ cd cryptsetup
alex@berbara:~/cryptsetup$ ./autogen.sh
< SNIPP >
config.status: creating po/Makefile
Now type `make' to compile the package.
alex@berbara:~/cryptsetup$ make
make all-recursive
< SNIPP >
alex@berbara:~/cryptsetup$ su - -c "make"
Password: root password
About cryptsetup
Because the way using dmsetup directly is too complicated for most people Christophe has written a native cryptsetup program thet behaves like one of the coach purses patched losetup's out there. The first essay version (v0.1) based on some of the native cryptsetup implementation in C is ready.cryptsetup 0.1 requires libgcrypt 1.1.x and libdevmapper
Don't forget to call scripts/devmap_mknod.sh (only once) in the device-mapper package to create the /dev/mapper/control device node if you don't use devfs or udev.
If you are interested in helping to develop cryptsetup contact Christophe about getting write access to his cvs server.
Logo Design
V0.1 Syntax
Syntax: /usr/local/sbin/cryptsetup <OPTIONS> <action> <name> <device>
<OPTIONS>:
-c <cipher> (see /proc/crypto)
-h {plain/<hash>} (see hashalot, WARNING: use ripemd160 instead of rmd160)
-y (verifies the passphrase by asking for it twice)
-d <file> (read key from file
e.g. /dev/urandom; useful for swap devices.
If set, the parameters -h and -y will be ignored)
-s <keysize> (in bits) (WARNING: in bytes for cryptsetup.sh)
-b <size> (in sectors)
-o <offset> (in sectors)
-p <skipped> (in sectors)
<action> is one of:
create - create device
remove - remove device
reload - modify active device
resize - resize active device
status - show device status
<name> is the device to create under /dev/mapper/
<device> is the encrypted device
When creating a device the program will ask for the a passphrase. The passphrase will then be hashed using the hashalot program and be used as key.
Alternatively a passphrase can be piped through stdin.
The hashing can be turned off with -h plain.
The defaults are aes with a 256 bit key, hashed using ripemd160.
Don't forget: cryptsetup only creates a mapping. If you call cryptsetup again after a reboot and supply the same passphrase you will be able to mount your filesystem you created before.
v0.1 - First Release
v0.1 - Can't mount files directly, use losetup first.
v0.1 - Can't mount read-only devices (CD/DVD-ROM's) use losetup first.
The latest version of cryptsetup is available by CVS. There is a web frontend to the CVS version here.
To check out the latest version from CVS do the following (keyboard input in bold):
^alex@berbara:~$ cvs -d:pserver:cvs@cvs.saout.de:/cvsroot/saout login
Logging in to :pserver:cvs@cvs.saout.de:2401/cvsroot/saout
CVS password: cvs
alex@berbara:~$ cvs -z3 -d:pserver:cvs@cvs.saout.de:/cvsroot/saout co cryptsetup
cvs server: warning: NULL value for key `All' at line 1 of `/cvsroot/saout/CVSROOT/modules'
cvs checkout: warning: NULL value for key `All' at line 1 of `/cvsroot/saout/CVSROOT/modules'
cvs checkout: Updating cryptsetup
U cryptsetup/AUTHORS
U cryptsetup/ChangeLog
U cryptsetup/Makefile.am
< SNIPP >
U cryptsetup/src/cryptsetup.c
U cryptsetup/src/cryptsetup.h
alex@berbara:~$ cd cryptsetup
alex@berbara:~/cryptsetup$ ./autogen.sh
< SNIPP >
config.status: creating po/Makefile
Now type `make' to compile the package.
alex@berbara:~/cryptsetup$ make
make all-recursive
< SNIPP >
alex@berbara:~/cryptsetup$ su - -c "make"
Password: root password
Created by: alex last modification: Thursday 05 of August, 2010 [12:37:39 UTC] by Anonymous
Page: 1/1
1
1
|
Page generated in: 0.12 seconds |
|
||||||||||||||
Login