Kernel detached from Encrypted Drive - can drive be rescued?

Asked by Life Fan

I have a few encrypted back up drives.

I encrypted them with relatively simple passwords / phrases, using a type of disk encryption, that connects the passphrase to the Linux Kernel. I actually thought it was a stand alone disk encryption that could be opened simply with what was on the disk.

Now a few computer systems later, I want to open them up and use them, AND the pass words do not work.

The problem as I see it is that the connection from the CPU - through the Linux OS, was that the other part of the function / pass phrase, was stored in the Linux Kernel - which allowed the encrypted drive to be opened up.

Now that the OS and OLD computer/s are long gone, the encrypted drives are still working / available but the pass phrases do not work, because the matching kernel / linux OS is not there to synch with the encypted drive.

This appears to be an unmentioned trap with using disk encryption.

Is there a way to open up an encrypted drive with it's passphrase, without the matching kernel?

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Manfred Hampl (m-hampl) said :
#1

I am not aware of any encryption program that needs a specific kernel version for decrypting.

Which program is this, which you have used for encryption?

Revision history for this message
Life Fan (llifandd) said :
#2

OK I might get the phrases and words wrong - so excuse the mix ups etc.

Ummmmm I recall that there are at least 2 LVM or Logical Volume Management's, being L2 and L8 in disk encryption.

I have only seen references to it in a couple of places, namely ONE line in a reply.

This is NOT the actual reply.... but it has the general thrust of the issue.

https://askubuntu.com/questions/320077/should-i-record-my-encryption-passphrase?rq=1

The passphrase unwrapper unwraps from a file stored on your system, likely in /home/.ecryptfs. It's just prudent to have another, off-system copy of this single point of failure for all your user data.

Yeah I just scrubbed the encryption and over wrote them, using initally Gparted - and because that IDIOT program decided to only grant ROOT access, and NONE of the native filing systems could open the drive with administrative rights so I could change the permissions, I then reformatted the disk with Disks, which made it a read write Exf4 drive without getting locked out.....

Revision history for this message
Manfred Hampl (m-hampl) said :
#3

What is now the status of this question?
Do you need further help?
If yes, then you should provide diagnostic information like Ubuntu release you are using, kernel version, LVM listings etc., e.g. the full output of the commands

uname -a
lsb_release -crid
sudo lvm pvscan
sudo lvm lvscan
sudo lvm vgscan

Revision history for this message
Launchpad Janitor (janitor) said :
#4

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.