One additional note for anyone still stuck using this trainwreck for
whatever reason:
Even if you use the keyctl hack to get mounting your private data to
work, you will be unable to UNmount it because of bugs in ecryptfs-
umount-private. The workaround for THAT bug is to just call
@foresto Thank you for the message & background info on systemd -- it's
very helpful to know when to give up trying.
In the end I followed your advice and stopped using ecrypts (I decrypted
my files in a Docker container running 18.04, as I already updated to
20.04 and could not get it to work).
I hate to say this, folks, but ecryptfs looks like a dead end for us.
It's no longer supported by Ubuntu (the package has been moved to the
Universe repo). Also, the problem at hand is caused by systemd, which is
run by a man famous for releasing poorly-vetted, system-breaking
software, and then
I am getting exactly the same issue here after upgrading from 18.04 to
20.04. I use a custom folder and have some shell utilities to run the
mount command with the right paramaters. Below SIG and FNEK_SIG continue
to match what `ecryptfs-add-passphrase --fnek` reports (and the same as
before the
Same issue here some time after upgrading from 16.04 lts to 18.04 lts. These
error messages appear after reboot:
[ 61.411306] Could not find key with description: [...]
[ 61.411344] Could not find valid key in user session keyring for sig specified
in mount option: [...]
[ 61.411383] Error
This is truly unfortunate -- my little media server started off life as
an Ubuntu Server 17.04 _Zesty Zapus_ VM, but has been working for years
now as 18.04.x and recently failed an upgrade to 20.04 i believe (at
least in part) due to this nagging issue. I'm not able to work around
it with my
I just upgraded from 16.04 to 18.04 and I'm seeing the same/similar
issue. I have the same messages in the log, and I have an encrypted
home folder.
When I *first* try to log in after a reboot, I get bounced back to the
login screen. It then logs in on the second attempt (so far - but this
This affects me too. I started seeing the error in dmesg after upgrading
from 16.04 to 18.04. Everything seems to work fine, but the message is
scary.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
#34 said:
This bug affects a cryptographic (read: highly sensitive) feature, is 15 months
old, a patch was proposed 12 months ago, but it is still of "Undecided"
importance and still "Unassigned"? Come on! Are the ecryptfs-utils and systemd
packages unmaintained at Ubuntu?
Well, this bug is
I have a completely encrypted home (auto configured) in bionic and have
the same error messages in dmesg. Moreover, since a few weeks ago, the
home directory sometimes gets broken in a way that all list requests
(ls, browse in nautilus) hang just on the home directory (process in S
state) and only
Still broken in disco.
** Tags added: disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718658
Title:
ecryptfs-mount-private fails to initialize ecryptfs keys
To manage notifications about
The systemd patch I posted earlier no longer works in disco, and the
workarounds posted here only partially fix the problem and only for a
subset of use cases. Looks like we're back to needing a proper fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Same here after upgrading Ubuntu Mate 18.04 to 19.04
** Also affects: ecryptfs
Importance: Undecided
Status: New
** No longer affects: ecryptfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Upgraded from Ubuntu server 16 to 18 and I too am having this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718658
Title:
ecryptfs-mount-private fails to initialize ecryptfs keys
To manage
I have just encountered this issue on 18.04 with Linux
4.15.0-54-generic.
The proposed workaround does not work for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718658
Title:
This error message is still pressent in my logs in XUbuntu 19.04
(freshly updated as of today). But the mounting finally occurs. However
it is still quite annoying...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I would not trust ecryptfs anymore.
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1756840
Use the time to migrate your data.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718658
Still the issue persist at present, Ubuntu 18.08 LTS.
The workaround suggested in the bug description works, but for how long I
wonder?
Would you trust this bugged ecryptfs to manage sensible data?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Still actual in 18.04.
This looks scary.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718658
Title:
ecryptfs-mount-private fails to initialize ecryptfs keys
To manage notifications about this
This bug affects me too
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718658
Title:
ecryptfs-mount-private fails to initialize ecryptfs keys
To manage notifications about this bug go to:
I could automate the workaround #26 and #30 but putting the said command
in my .profile
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718658
Title:
ecryptfs-mount-private fails to initialize
Trying to mount a personnal dir (not home) with ecryptfs-simple fails, with the
same error messages in kern.log as comment #20. (Using Linux Mint 19, Xfce.)
The workaround in comments #26 and #30 works for me. (No sudo like in #28 :
with sudo the mount works but the key sig gets added to
I had updated my laptop so to Ubuntu 18.10 64bit and the message is
still present for me.
I see the messages (Could not find key with description...) in dmesg
output but all works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm using 18.04, everything up to date.
ecryptfs is used for home encryption. Everything seems to work fine, but error
messages (as already noted above) appears. Not to repeat everything already
said, additional note could be that the messages are not tagged where they
really comes from. It is
This started happening after installing lubuntu-desktop. Even after
removing it, it is still failing to mount. After running "keyctl link @u
@s", it works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Note: I'm using 18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718658
Title:
ecryptfs-mount-private fails to initialize ecryptfs keys
To manage notifications about this bug go to:
I see the messages (starting with "Could not find key with description")
on a fresh install of Linux Mint 19 Cinnamon.
Second line of kern.log says: "Linux version 4.15.0-36-generic
(buildd@lgw01-amd64-031) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3))
#39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018
#26 fixed this for me.
Doing a manual mount like so (used for safely storing private data in
the cloud) used to work since Ubuntu 12 or so.
However, today after updating from Ubuntu 16.04 LTS to 18.04 LTS, the
entire thing wouldn't mount anymore:
```
$ echo mypassphrase | sudo
Something intriguing is that I updated to a 18.04 when it was still not
released (I don't know if it was beta or not. I did it in March. Everything was
fine. Everything mounted without any workaround with: mount.ecryptfs_private
blabla
Suddenly around April when new updates came, it went back
I had the same problem with Debian.
The workaround I used is creating a link from the key to the keyring
keyctl link @u @s
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718658
Title:
Ooops, no, sorry, it works (/tmp/a was missing).
So the kernel is definitely able to mount the file systems, it's just
that ecryptfs-utils and their key management do not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Even a direct
mount -t ecryptfs -o
ecryptfs_check_dev_ruid,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs
/tmp/work /tmp/a
fails with
[-2] No such file or directory
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Please keep in mind that ecryptfs-mount-private and
mount.ecryptfs_private are slightly different things.
Since ecryptfs-mount-private is a frontend to the underlying
mount.ecryptfs_private, and this isn't working either (also not under
18.04), it is vital to focus on fixing that.
I found that
ecryptfs (private mount) still does not work under 18.04.
That's a complete showstopper for the upgrade 16.04->18.04 because access to
encrypted files becomes impossible or at least troublesome.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Ok, so I restored my system and I got back to my Mate and all my settings are
kept.
I did a lot of things, even removed ecryptfs while extracted all my home
directory from it.
I removed NVidia drivers but I don't think that they caused the problem.
But only reinstalling of XServer finally
Same as @stokito happened to me. Yesterday I upgraded to Kubuntu 18.04
via "do-release-upgrade" command from a previous install of Kubuntu
17.10 did some half a year ago. When I restart the system I see the
Kubuntu Plymouth start screen but then it never arrives to the login
screen (sddm). I can
I upgraded from Ubuntu Mate 17.10 to 18.04 after reboot I passed GRUB then I
saw logo of Ubuntu Mate and then by screen become black witout anything.
I pressed Ctrl+F1 and swithed to tty1 then logged in and it show me three last
errors from dmesg and firts was:
"could not find valid key in user
Same as @Thorsten and @callegar. I see the error messages but everything works
fine.
I also just upgraded to 18.04 from a fresh install of 17.10 and the errors are
still present.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I don't agree with the last comme,nt : I have a fresh install of 18.04
and get the same error when trying to recover my old savec Private
directory :
Enter your MOUNT passphrase:
mount: /tmp/ecryptfs.fSC9TkTG : échec de l’appel système mount(2) : Aucun
fichier ou dossier de ce type.
ERROR:
This doesn't happen in 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718658
Title:
ecryptfs-mount-private fails to initialize ecryptfs keys
To manage notifications about this bug go to:
The attachment "disable_system_service_session_keyrings.patch" seems to
be a patch. If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a
A systemd build with my patch applied is available here:
https://launchpad.net/~foresto/+archive/ubuntu/ubuntutweaks/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718658
Title:
This is a systemd bug, created by this commit:
https://github.com/systemd/systemd/commit/74dd6b5
It looks like poettering has attempted to address it in more recent
versions of systemd (though that doesn't help us in ubuntu 17.10):
https://github.com/systemd/systemd/pull/6832
--
You received
Here's a simple patch to disable the broken systemd feature, and restore
ecryptfs functionality.
** Patch added: "disable_system_service_session_keyrings.patch"
The ecryptfs-manager workaround helps the mount to succeed, but (at
least in my case) the system refuses to unmount it afterward. This is a
problem for those of us who open our ecryptfs volumes only for as long
as they're needed.
--
You received this bug notification because you are a member of
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718658
Title:
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718658
Title:
ecryptfs-mount-private fails to initialize ecryptfs keys
Okay, the issue with failing X server in my case was not relevant to the
encryption errors and was resolved by completing the upgrade process properly:
sudo apt-get update && sudo apt-get dist-upgrade
So this one was more related to the broken upgrade process for 17.04-17.10, so
please disregard
I faced the same issue after upgrading from Ubuntu 17.04 to 17.10 a day ago.
I'm having my home directory encrypted and I'm getting the same error message
after every first login.
My home directory is mounted correctly though.
As an even worst consequense I'm not able to login into grafical
I see the same as @Thorsten. I have an encrypted Private directory. If I
log into my user account the directory is correctly mounted. However, I
still see the same error message as @Thorsten via dmesg.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
i have to add that this message only occurs on the first login after a
reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718658
Title:
ecryptfs-mount-private fails to initialize ecryptfs keys
i have a fresh ubuntu 17.10 installation with an encrypted home (so all
auto configured). If i log into my user account it all works fine.
However i also get that error message in dmsg:
[ 55.425188] Could not find key with description: [...]
[ 55.425191] process_request_key_err: No key
[
Exact same problem here. I am using a custom ecryptfs folder (always
worked for 3 years). Only way to mount it was by running ecryptfs-
manager first.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ecryptfs-utils (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718658
** Tags added: artful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718658
Title:
ecryptfs-mount-private fails to initialize ecryptfs keys
To manage notifications about this bug go to:
It is Artful... Sorry!
brill@tapir:~$ dpkg -l | grep ecrypt
ii ecryptfs-utils 111-0ubuntu4
amd64ecryptfs cryptographic filesystem (utilities)
ii libecryptfs1 111-0ubuntu4
Hello
Can you please add a tag for the version of Ubuntu you are using? (Xenial,
Zesty, Artful)
** Also affects: ecryptfs-utils (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-mate
--
You received this bug notification because you are a member of Ubuntu
Bugs,
57 matches
Mail list logo
