Linux ih01.iridiumhosting.com 5.14.0-611.55.1.el9_7.x86_64 #1 SMP PREEMPT_DYNAMIC Tue May 19 15:19:29 EDT 2026 x86_64
LiteSpeed
Server IP : 67.227.241.211 & Your IP : 216.73.216.158
Domains :
Cant Read [ /etc/named.conf ]
User : dustinhy
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
opt /
MXB /
rear /
usr /
share /
rear /
finalize /
GNU /
Linux /
Delete
Unzip
Name
Size
Permission
Date
Action
230_remove_lvmdevices.sh
1019
B
-rw-r--r--
2026-04-01 09:39
240_reassign_luks_keyfiles.sh
2.45
KB
-rw-r--r--
2026-04-01 09:39
250_migrate_disk_devices_layout.sh
4.92
KB
-rw-r--r--
2026-04-01 09:39
250_migrate_lun_wwid.sh
3.54
KB
-rw-r--r--
2026-04-01 09:39
260_rename_diskbyid.sh
7.39
KB
-rw-r--r--
2026-04-01 09:39
280_migrate_uuid_tags.sh
3.4
KB
-rw-r--r--
2026-04-01 09:39
300_create_mac_mapping.sh
846
B
-rw-r--r--
2026-04-01 09:39
310_migrate_udev_rules.sh
2.78
KB
-rw-r--r--
2026-04-01 09:39
320_migrate_network_configuration_files.sh
33.93
KB
-rw-r--r--
2026-04-01 09:39
430_create_multipath_config.sh
1.55
KB
-rw-r--r--
2026-04-01 09:39
Save
Rename
# Re-assign original keyfiles to LUKS volumes # # In the 'layout/prepare' stage, temporary keyfiles were generated for password-less decryption. By now, the # original keyfiles should have been restored from the backup. If so, the original keyfiles are re-assigned # to their LUKS volumes and temporary keyfiles are discarded. Where an original keyfile was not restored # to its expected location, an error message is displayed and the corresponding temporary keyfile will take # over, so that the recovered system remains fully functional. local target_name source_device original_keyfile awk ' $1 == "crypt" && / keyfile=/ { target_name = $2; sub("^/dev/mapper/", "", target_name); source_device = $3; sub("^.* keyfile=", ""); sub("[ \t].*$", ""); original_keyfile = $0; print target_name, source_device, original_keyfile; } ' "$LAYOUT_FILE" | while read target_name source_device original_keyfile; do Log "Re-assigning keyfile $original_keyfile to LUKS device $target_name ($source_device)" # The scheme for generating a temporary keyfile path must be the same here and in the 'layout/prepare' stage: temp_keyfile="$TMP_DIR/LUKS-keyfile-$target_name" test -f "$temp_keyfile" || BugError "temporary LUKS keyfile $temp_keyfile not found" target_keyfile="$TARGET_FS_ROOT/$original_keyfile" if [ -f "$target_keyfile" ]; then # Assign the original keyfile to the LUKS volume, if successful, remove the temporary keyfile. cryptsetup --key-file "$temp_keyfile" luksAddKey "$source_device" "$target_keyfile" BugIfError "Could not add the keyfile $original_keyfile to LUKS device $target_name ($source_device)" cryptsetup luksRemoveKey "$source_device" "$temp_keyfile" BugIfError "Could not remove the temporary keyfile $temp_keyfile from LUKS device $target_name ($source_device)" else # The original keyfile was not restored from the backup - move the temporary keyfile to # the target location so that the LUKS volume can still be decrypted. mkdir -p "$(dirname $target_keyfile)" cp -p "$temp_keyfile" "$target_keyfile" && rm "$temp_keyfile" StopIfError "Could not restore keyfile $original_keyfile for LUKS device $target_name ($source_device) from temporary keyfile" LogPrintError "$original_keyfile was not restored from the backup - LUKS device $target_name ($source_device) has been assigned a new keyfile" fi done