OXIESEC PANEL
- Current Dir:
/
/
usr
/
share
/
doc
/
cryptsetup
Server IP: 139.59.38.164
Upload:
Create Dir:
Name
Size
Modified
Perms
📁
..
-
11/10/2024 09:42:49 AM
rwxr-xr-x
📄
AUTHORS
102 bytes
03/07/2018 11:55:54 AM
rw-r--r--
📄
FAQ.gz
42.41 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
NEWS.Debian.gz
3.57 KB
03/18/2018 01:01:09 AM
rw-r--r--
📄
README.Debian.gz
5.05 KB
03/18/2018 01:01:09 AM
rw-r--r--
📄
README.gnupg
1.59 KB
03/18/2018 01:01:09 AM
rw-r--r--
📄
README.initramfs.gz
4.15 KB
03/18/2018 01:01:09 AM
rw-r--r--
📄
README.keyctl
3.04 KB
03/18/2018 01:01:09 AM
rw-r--r--
📄
README.openct.gz
2.34 KB
03/18/2018 01:01:08 AM
rw-r--r--
📄
README.opensc.gz
2.23 KB
03/18/2018 01:01:09 AM
rw-r--r--
📄
TODO.Debian
3.58 KB
03/18/2018 01:01:09 AM
rw-r--r--
📄
changelog.Debian.gz
2.94 KB
08/03/2020 09:28:48 PM
rw-r--r--
📄
copyright
4.83 KB
03/18/2018 01:01:09 AM
rw-r--r--
📁
examples
-
05/09/2024 07:14:02 AM
rwxr-xr-x
📄
v1.0.7-ReleaseNotes
2.85 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.1.0-ReleaseNotes.gz
2.22 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.1.1-ReleaseNotes
1.75 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.1.2-ReleaseNotes
1.56 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.1.3-ReleaseNotes
482 bytes
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.2.0-ReleaseNotes.gz
2.07 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.3.0-ReleaseNotes.gz
2.08 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.3.1-ReleaseNotes
421 bytes
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.4.0-ReleaseNotes.gz
2.2 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.4.1-ReleaseNotes
889 bytes
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.4.2-ReleaseNotes
1.59 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.4.3-ReleaseNotes
2.3 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.5.0-ReleaseNotes.gz
3.24 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.5.1-ReleaseNotes
1.26 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.6.0-ReleaseNotes.gz
3.73 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.6.1-ReleaseNotes
1.02 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.6.2-ReleaseNotes
985 bytes
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.6.3-ReleaseNotes
1.82 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.6.4-ReleaseNotes
1.99 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.6.5-ReleaseNotes
2.42 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.6.6-ReleaseNotes
1.07 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.6.7-ReleaseNotes
3.25 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.6.8-ReleaseNotes
2.01 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.7.0-ReleaseNotes
3.03 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.7.1-ReleaseNotes
1.34 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.7.2-ReleaseNotes
1.45 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.7.3-ReleaseNotes
811 bytes
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.7.4-ReleaseNotes
657 bytes
03/07/2018 11:55:54 AM
rw-r--r--
📄
v1.7.5-ReleaseNotes
833 bytes
03/07/2018 11:55:54 AM
rw-r--r--
📄
v2.0.0-ReleaseNotes.gz
9.5 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v2.0.1-ReleaseNotes.gz
2.17 KB
03/07/2018 11:55:54 AM
rw-r--r--
📄
v2.0.2-ReleaseNotes.gz
1.95 KB
03/07/2018 11:55:54 AM
rw-r--r--
Editing: README.gnupg
Close
using GnuPG keys for LUKS dm-crypt devices in Debian ---------------------------------------------------- The Debian cryptsetup package provides the keyscript decrypt_gnupg for setups with a GnuPG encrypted LUKS keyfile. The following example assumes that you store the encrypted keyfile in /etc/keys/cryptkey.gpg. LUKS device is /dev/<luks_device>. First, you'll have to create the encrypted keyfile: # dd if=/dev/random bs=1 count=256 | gpg --no-options --no-random-seed-file \ --no-default-keyring --keyring /dev/null --secret-keyring /dev/null \ --trustdb-name /dev/null --symmetric --output /etc/keys/cryptkey.gpg Next the LUKS device needs to be formated with the key. For that, the decrypt_gnupg keyscript can be used: # /lib/cryptsetup/scripts/decrypt_gnupg /etc/keys/crytpkey.gpg | \ cryptsetup --key-file=- luksFormat /dev/<luks_device> In order to unlock the encrypted LUKS device automatically during boot process, add the following to /etc/crypttab: cdev1 /dev/<luks_device> /etc/keys/cryptkey.gpg luks,keyscript=decrypt_gnupg decrypting the keyfile at initramfs stage ----------------------------------------- If the device is to be unlocked at initramfs stage (such as for the root FS or the resume device), the provided initramfs hooks should do all additionally required work for you when the initramfs is created or updated. Be warned though, that for such devices the GnuPG encrypted key is copied to the initramfs by the initramfs cryptgnupg hook. If you don't want this, you should take a look at the initramfs cryptgnupg hook, which is located at /usr/share/initramfs-tools/hooks/cryptgnupg.