C'est la troisième fois que je renonctre le même problème avec ecryptfs, je vais finir par le retenir :

#eCryptfs et les conteneurs c'est pas tenable !

c'est le support idmapped qui n'est pas dans ecryptfs, et c'est un besoin dans mon cas pour #incus pour qu'il puisse partager un répertoire entre l'invité et l'hôte.

mes serveur sont en luks, mais mes desktops, surtout ubutnut sont en ecryptfs ... Je finirai bien par tout passer en luks ...
@matrss @mahlzahn I am still running #ecryptfs on this system here (which #nixos has recently deprecated btw, damn!), and this even only supports 144 chars for filenames. Recently @forgejo's repo contains long test file names, making it a pain to work with on such filesystems.

Great, ecryptfs was dropped from nixpkgs, because apparently it wasn't updated in 10 years 😑

ecrypts was always my go-to solution for encrypting only my home directory, if full disk encryption is not available.

So what does one use now for homedir encryption?

https://github.com/NixOS/nixpkgs/pull/479934

#ecryptfs #nixos #nixpkgs

ecryptfs: drop by Sigmanificient · Pull Request #479934 · NixOS/nixpkgs

While looking into python2 remaining bits, i come across this package, and it seems appropriate to remove it. ecryptfs hasn't been updated sine May 2016, and seems to have questionable maintena...

GitHub

Still no clue where the issue is that's why asking again:

i have an encrypted LUKS system partition (that got boot killed by win11). If i want to access from a live-USB it asks for the password (obviously). I am 100% sure the password is correct, but i get a "false password" error.

Even tried different kb-layouts to check the us-ger mapping differences.

I'm out of ideas. Anyone!?

#linux #encryption #luks #ecryptfs

Well OMZ have i ever been in a bit of a digital flap here, for the past few hours 😳

Was happily pooterising away on Lappy, in the Sunroom, as is my wont in winter coz the Study wherein lives
main pooter Tower tends to be a bit chilly in the morns. All was going tikkettyboo when all of a sudden... it wasn't. 😮

#ReallyWeirdShit began happening. Apps stopped working, stopped even launching. In #LMDE's file manager, my directories & files began disappearing. Soon, eventually, everything in my Home directory was gorn, replaced merely with two directories for #eCryptfs, being .ecryptfs & .Private.

I badly struggled to even conceive what might have just happened, having never experienced anything like this before. My misanthropic
glass half empty self soon suspected that somehow, inexplicably, Lappy had just copped a malicious attack from someone who disables victim's pooters by covertly running some malware that encrypts all the user's data files. 😱

But... how? How the fsck? This ain't windoze, it's Linux? What even was the vector? By definition there's been no local attack, as only my two teddybears & me are here. How though could it have been a remote attack? I do not go about downloading random files from dodgy sites. My browsers are very hardened, explicitly to make difficult or impossible any drive-by attacks from compromised sites.

Completely flummoxed, i accepted that there was nothing more i could do to try to salvage Lappy, aside from a reinstallation beginning with wiping the SSD, & hoping like hell the UEFI firmware hasn't been infected. Feeling sick in the tummy with worry about exactly what happened & how, wrt what could i do differently to guard against repeat attacks, i resigned myself to this course of action. First though, i decided to fully shutdown then cold boot, in order to at least have the intellectual satisfaction of getting to see the anticipated hijack / ransomware screen.

Shutdown. Booted. Unlocked the SSD password. Still all normal. Unlocked the LMDE encryption. Still all normal. Logged into the Cinnamon desktop... hey wait a tick, that should not have been possible, if all my
Home is locked away! Desktop looks & behaves like normal. Apps launch & run fine. File manager shows all my data is there, fine & dandy.

Wtaf?
😮🤯🤷

TLDR
I do not now believe there was any attack. I belatedly remembered that unlike my Tower's
#ArchLinux which uses #LUKS #encryption, LMDE uses... eCryptfs. Uh. I suspect that something caused LMDE to experience a serious integrity problem as i pooterised away on it this morn, such that somehow it re-encrypted itself in operation... which should never occur, & is clearly a serious problem. Happily the reboot resolved it, & most happily i can stop worrying about having been hacked. Neither of those however ameliorate the fact that a few high-stress hours have been lost to this shitfuckery. 🥺
Dimanche sécurité 😏
Je n'avais aucunes excuses, surtout en étant dans l'informatique ❗
Les ordinateurs de madame, et les miens, n'étaient pas chiffrés ❗
Toutes les machines (desktop/laptop) Windows et Linux sont maintenant chiffrés 👌
J'ai opté pour plus de flexibilité au détriment d'un peu de performance, c'est donc #Veracrypt pour Windows, et #ecryptfs pour Linux 😎

As I understand it, full disk encryption currently does not work with #PostmarketOS, at least with v24.12. (pmbootstrap-installation with FDE does not boot on my PinephonePro...)

As a Plan B I tried to set up #ecryptfs but the kernel module is missing.

Does anybody have a good solution for encrypting at least home on @postmarketOS?

I am looking into getting my #PinephonePro in a state so that it can be used as a daily driver but encryption is mandatory then of course...

It seems that I outsmarted myself and made my old home directory #ecryptfs. Until I have something other than this low-end #Windows box, I locked myself out of my own files.
Securing Your Digital Fortress Implementing a Linux Filesystem Encryption With LUKS and eCryptfs | Linux Journal

Wondering if there would be a way to sort #ecryptfs and #ssh conflict with a PAM module for #OpenSSH that would sort of “plug out” the #authentication part. AFAIK this problem comes from “non-standard” authentication path of OpenSSH: it ignores PAM and does its own thing.
Akkoma