From: Tyler Hicks <tyhicks@canonical.com>
To: Marc de Verdelhan <mdeverdelhan@gmail.com>
Cc: ecryptfs@vger.kernel.org
Subject: Re: Way to decrypt an encrypted /home
Date: Wed, 1 Apr 2015 09:42:12 -0500 [thread overview]
Message-ID: <20150401144211.GA11872@boyd> (raw)
In-Reply-To: <CAHTahaZZetDg8=X=G4rTRJJWJBRXrN4N1dK86kUqwOXXKhh7bQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2673 bytes --]
On 2015-04-01 09:52:49, Marc de Verdelhan wrote:
> Hi there,
Hello! Sorry to hear about the trouble you're having.
>
> I made a huge mistake and I need some help.
>
> I was running Linux Mint 17 (based on Ubuntu 14.04) with an encrypted
> home directory (using eCryptfs). /home and / were on separated
> partitions.
> Last week I replaced Mint by Debian. I formatted the / partition and
> kept the /home one. Now I can't decrypt my data. :/
Did you record the randomly generated mount passphrase? After you set up
an encrypted home directory in Ubuntu, you receive a pop up dialogue box
informing you to record the mount passphrase and keep it somewhere safe.
If you followed that advice, we can save a lot of time debugging the
issue below.
Tyler
>
> So I installed the ecryptfs-utils package.
>
> "ecryptfs-mount-private" returns:
> Error: Unwrapping passphrase and inserting into the user session
> keyring failed [-5]
> Info: Check the system log for more information from libecryptfs
> ERROR: Your passphrase is incorrect
>
> "/var/log/syslog" contains:
> ecryptfs-insert-wrapped-passphrase-into-keyring: Incorrect wrapping
> key for file [/home/login/.ecryptfs/wrapped-passphrase]
> ecryptfs-insert-wrapped-passphrase-into-keyring: Error attempting to
> unwrap passphrase from file
> [/home/login/.ecryptfs/wrapped-passphrase]; rc = [-5]
>
> "ecryptfs-unwrap-passphrase
> /home/.ecryptfs/login/.ecryptfs/wrapped-passphrase" returns:
> Error: Unwrapping passphrase and inserting into the user session
> keyring failed [-5]
> Info: Check the system log for more information from libecryptfs
>
> To be sure I reinstalled the original Linux Mint on the / partition,
> using the same login:password as before my misfortune. Same results.
> I'm ABSOLUTELY sure that I'm using the same login and password than
> last week. I installed Linux Mint 17 on June 2014; the ecryptfs-utils
> version should have been "104-0ubuntu1".
>
> So questions are:
> 1) What happened? Did I erase a configuration file I shouldn't? I
> would like to understand what operation occurred to be in that
> unpleasant situation?
>
> 2) What are my options? It may involve some C development if needed.
> According to you, is there a way to brute force something? Or a more
> intelligent solution, starting with sit down, have a tea and think.
>
> Any help will be greatly appreciated. Thank you for reading.
>
> Marc
> --
> To unsubscribe from this list: send the line "unsubscribe ecryptfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-04-01 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 7:52 Way to decrypt an encrypted /home Marc de Verdelhan
2015-04-01 14:42 ` Tyler Hicks [this message]
2015-04-03 12:48 ` Marc de Verdelhan
2015-04-21 10:57 ` Pablo Castellano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150401144211.GA11872@boyd \
--to=tyhicks@canonical.com \
--cc=ecryptfs@vger.kernel.org \
--cc=mdeverdelhan@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox