Linux web-conference.aiou.edu.pk 5.4.0-205-generic #225-Ubuntu SMP Fri Jan 10 22:23:35 UTC 2025 x86_64
Apache/2.4.41 (Ubuntu)
: 172.16.50.247 | : 18.118.9.230
Cant Read [ /etc/named.conf ]
7.4.3-4ubuntu2.28
root
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
BLACK DEFEND!
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
cryptsetup /
[ HOME SHELL ]
Name
Size
Permission
Action
examples
[ DIR ]
drwxr-xr-x
AUTHORS
137
B
-rw-r--r--
FAQ.gz
42.4
KB
-rw-r--r--
Keyring.txt
2.66
KB
-rw-r--r--
LUKS2-locking.txt
2.65
KB
-rw-r--r--
NEWS.Debian.gz
1.03
KB
-rw-r--r--
README.Debian.gz
5.39
KB
-rw-r--r--
README.debug
2.67
KB
-rw-r--r--
README.gnupg
1.8
KB
-rw-r--r--
README.gnupg-sc
2.29
KB
-rw-r--r--
README.keyctl
3.5
KB
-rw-r--r--
README.opensc.gz
2.22
KB
-rw-r--r--
changelog.Debian.gz
2.01
KB
-rw-r--r--
copyright
8.5
KB
-rw-r--r--
v1.0.7-ReleaseNotes
2.85
KB
-rw-r--r--
v1.1.0-ReleaseNotes.gz
2.22
KB
-rw-r--r--
v1.1.1-ReleaseNotes
1.75
KB
-rw-r--r--
v1.1.2-ReleaseNotes
1.56
KB
-rw-r--r--
v1.1.3-ReleaseNotes
482
B
-rw-r--r--
v1.2.0-ReleaseNotes.gz
2.07
KB
-rw-r--r--
v1.3.0-ReleaseNotes.gz
2.08
KB
-rw-r--r--
v1.3.1-ReleaseNotes
421
B
-rw-r--r--
v1.4.0-ReleaseNotes.gz
2.2
KB
-rw-r--r--
v1.4.1-ReleaseNotes
889
B
-rw-r--r--
v1.4.2-ReleaseNotes
1.59
KB
-rw-r--r--
v1.4.3-ReleaseNotes
2.3
KB
-rw-r--r--
v1.5.0-ReleaseNotes.gz
3.24
KB
-rw-r--r--
v1.5.1-ReleaseNotes
1.26
KB
-rw-r--r--
v1.6.0-ReleaseNotes.gz
3.73
KB
-rw-r--r--
v1.6.1-ReleaseNotes
1.02
KB
-rw-r--r--
v1.6.2-ReleaseNotes
985
B
-rw-r--r--
v1.6.3-ReleaseNotes
1.82
KB
-rw-r--r--
v1.6.4-ReleaseNotes
1.99
KB
-rw-r--r--
v1.6.5-ReleaseNotes
2.42
KB
-rw-r--r--
v1.6.6-ReleaseNotes
1.07
KB
-rw-r--r--
v1.6.7-ReleaseNotes
3.25
KB
-rw-r--r--
v1.6.8-ReleaseNotes
2.01
KB
-rw-r--r--
v1.7.0-ReleaseNotes
3.03
KB
-rw-r--r--
v1.7.1-ReleaseNotes
1.34
KB
-rw-r--r--
v1.7.2-ReleaseNotes
1.45
KB
-rw-r--r--
v1.7.3-ReleaseNotes
811
B
-rw-r--r--
v1.7.4-ReleaseNotes
657
B
-rw-r--r--
v1.7.5-ReleaseNotes
833
B
-rw-r--r--
v2.0.0-ReleaseNotes.gz
9.5
KB
-rw-r--r--
v2.0.1-ReleaseNotes.gz
2.17
KB
-rw-r--r--
v2.0.2-ReleaseNotes.gz
1.95
KB
-rw-r--r--
v2.0.3-ReleaseNotes.gz
2.39
KB
-rw-r--r--
v2.0.4-ReleaseNotes.gz
2.27
KB
-rw-r--r--
v2.0.5-ReleaseNotes.gz
2.02
KB
-rw-r--r--
v2.0.6-ReleaseNotes.gz
1.91
KB
-rw-r--r--
v2.1.0-ReleaseNotes.gz
3.4
KB
-rw-r--r--
v2.2.0-ReleaseNotes.gz
4.47
KB
-rw-r--r--
v2.2.1-ReleaseNotes
1.38
KB
-rw-r--r--
v2.2.2-ReleaseNotes
2.1
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : README.gnupg-sc
rUing OpenPGP smartcard for LUKS dm-crypt devices in Debian =========================================================== The Debian cryptsetup package provides the keyscript `decrypt_gnupg-sc` for setups with a keyfile that is encrypted using an OpenPGP smartcard. 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 keyfile and encrypt it with your key 0xDEADBEEF: dd if=/dev/random bs=1 count=256 | gpg --recipient 0xDEADBEEF \ --output /etc/keys/cryptkey.gpg --encrypt Next the LUKS device needs to be formated with the key. For that, the `decrypt_gnupg-sc` keyscript can be used: /lib/cryptsetup/scripts/decrypt_gnupg-sc /etc/keys/cryptkey.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-sc In order to avoid data loss if the smartcard is damaged or lost, you may want to decrypt `/etc/keys/cryptkey.gpg` and store the plaintext in a safe place. Or alternatively, use another slot with your backup key: cryptsetup luksAddKey /dev/<luks_device> /path/to/backup.key 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), you need to copy the public part of the encryption key to `/etc/cryptsetup-initramfs/pubring.gpg`: gpg --export 0xDEADBEEF >/etc/cryptsetup-initramfs/pubring.gpg Then 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 OpenPGP encrypted key is copied to the initramfs by the initramfs cryptgnupg-sc hook. If you don't want this, you should take a look at the initramfs cryptgnupg-sc hook, which is located at `/usr/share/initramfs-tools/hooks/cryptgnupg-sc`. Moreover, note that unlocking at initramfs stage is currently not compatible with plymouth or other bootsplash, as a curses-based prompt is used for PIN entry. -- Guilhem Moulin <guilhem@guilhem.org> Sun, 23 Sep 2018 03:28:31 +0200
Close
