ecryptfs-recover-private not working in Nabia

1 reply [Last post]
sid
sid
Offline
Joined: 02/09/2022

I tried out Nabia using a live USB, and I found that ecryptfs-recover-private fails with the message:

mount: mount(2) failed: No such file or directory
ERROR: Failed to mount private data at [/tmp/ecryptfs.XXXXXXXX]

By contrast, when I use a live USB running Flidas, ecryptfs-recover-private works just fine "out of the box".

If I run Nabia on a live USB, I can still recover ecryptfs directories the "manual" way (i.e. adding the passphrase and then mounting the encrypted directory), although this method is less convenient and rather unwieldy by comparison.

Strangely enough, if I run ecryptfs-recover-private after first recovering the encrypted directory the "manual" way, ecryptfs-recover-private works without any problems!

I have seen there are some old threads on Ubuntu and Arch forums which indicate that people have already encountered what appears to be the same problem with ecryptfs-recover-private years ago, without any resolution:

https://askubuntu.com/questions/659242/problem-with-ecryptfs-recover-private-mount2-failed

https://bbs.archlinux.org/viewtopic.php?id=181183

My first question then is what has changed between Flidas and Nabia that lets me use ecryptfs-recover-private fine on a live Flidas system but when I run the same command on a live Nabia system (or a live Etonia system for that matter), I encounter an error.

And my second question is why (using Nabia) ecryptfs-recover-private works as expected after already recovering the encrypted directory the "manual" way, but fails if executed without first using the manual recovery method.

I have no idea if this issue has to do with a bug in the ecryptfs-recover-private script, a bug in the Linux (or Linux libre) kernel, a bug in Trisquel, or something else alltogether. On the face of it, this looks like a regressive bug — something which works in Flidas doesn't work in Etonia or Nabia — but that is probably a naive assumption. I might guess that there is a latent bug in ecryptfs-recover-private which is dormant in Flidas but which gets triggered by changes to Trisquel made in Etonia/Nabia, but that is pure speculation on my part. Is anyone here able to shed some light on this? Nabia looks really good from what I have seen so far, only the issue with ecryptfs-recover-private hampers my experience and discourages me from using Nabia more.

By the way, I'm new here so I'm not sure if I am supposed to post this type of thing here in the forum or in the "issues" section of the website, let me know if I should create a new issue instead.

sid
sid
Offline
Joined: 02/09/2022

Just wanted to bump this thread in case it got overlooked while someone might have a simple solution or explanation.

Also is it worth opening an "issue" to track this problem?