F5F Stay Refreshed Software Operating Systems Verified restart of Ubuntu

Verified restart of Ubuntu

Verified restart of Ubuntu

R
RepoRizer
Posting Freak
872
12-27-2016, 10:03 PM
#1
You're facing a common challenge with encrypted systems. Since your desktop is locked with Luks, you can't just bypass the password during a reboot. However, you might explore options like using a recovery agent or adjusting your system's boot settings to allow password entry at shutdown instead of requiring it during startup. Consult your Ubuntu documentation for specific steps related to recovery and boot configurations.
R
RepoRizer
12-27-2016, 10:03 PM #1

You're facing a common challenge with encrypted systems. Since your desktop is locked with Luks, you can't just bypass the password during a reboot. However, you might explore options like using a recovery agent or adjusting your system's boot settings to allow password entry at shutdown instead of requiring it during startup. Consult your Ubuntu documentation for specific steps related to recovery and boot configurations.

M
marbleman2012
Junior Member
2
01-08-2017, 04:52 AM
#2
Accessing a LUKS-protected root drive from afar using SSH
An older piece of content that fits your request
M
marbleman2012
01-08-2017, 04:52 AM #2

Accessing a LUKS-protected root drive from afar using SSH
An older piece of content that fits your request

B
byDani_SMP
Member
59
01-09-2017, 03:18 PM
#3
I'm uncertain about how that addresses the BasicAMods question. Generally, I believe it's not wise to attempt what you want yourself. You should keep the password in plain text securely (as shown in the example where unlocking happens via SSH), which could be acceptable for you, but it poses a significant security risk if someone gains access to the file containing your password—this might render encryption unnecessary. In cases where you need the computer to detect reboots or power-offs, these situations are essentially identical from the device's perspective. You'll likely need to store the encryption key in something that remains active after reboots (though not during power loss), which still introduces security concerns.
B
byDani_SMP
01-09-2017, 03:18 PM #3

I'm uncertain about how that addresses the BasicAMods question. Generally, I believe it's not wise to attempt what you want yourself. You should keep the password in plain text securely (as shown in the example where unlocking happens via SSH), which could be acceptable for you, but it poses a significant security risk if someone gains access to the file containing your password—this might render encryption unnecessary. In cases where you need the computer to detect reboots or power-offs, these situations are essentially identical from the device's perspective. You'll likely need to store the encryption key in something that remains active after reboots (though not during power loss), which still introduces security concerns.

H
Houdi_Booty
Member
64
01-15-2017, 06:01 AM
#4
Thank you for your responses.
H
Houdi_Booty
01-15-2017, 06:01 AM #4

Thank you for your responses.

H
HolyNight98
Member
187
01-15-2017, 07:08 AM
#5
The key file required is the SSH key, not the Luks key. If you wish to follow the approach from the article, replace "MyS3cr3tK3y" with your real password. If it’s still current, it should function. To prevent others from accessing your password in your bash history, disable it in the present shell: unset HISTFILE. This change applies only to the terminal you’re using and won’t impact the rest of your system.
H
HolyNight98
01-15-2017, 07:08 AM #5

The key file required is the SSH key, not the Luks key. If you wish to follow the approach from the article, replace "MyS3cr3tK3y" with your real password. If it’s still current, it should function. To prevent others from accessing your password in your bash history, disable it in the present shell: unset HISTFILE. This change applies only to the terminal you’re using and won’t impact the rest of your system.