cryfs VS apfs-fuse

I know that cryfs[1] is resilient to at least the first of these, and possibly the second as well. I don't know if cryfs allows to modify the base directory while the filesystem is online, if it does then it might already be a better solution for syncthing, if you only care about Linux.

On the flip side syncthing could incorporate cryfs's base directory format instead of their home-grown one.

[1] https://www.cryfs.org/

When I tried cryfs mounting via file system, cryfs told me there was no vault at my vault directory. It says specifically, "Could not find base directory. Do you want to create it?"

you have a couple options. if you’re using ext4, fscrypt might be your best bet. if not, a FUSE-based encryption option is probably your only option. ecryptfs, gocryptfs and encfs are good, but i personally prefer cryfs. it doesn’t have an archwiki page, but can be installed from the repos and instructions for use can be found on its webpage

Cryfs encryption for future Cloud Storage = https://www.cryfs.org/

It sounds like cryfs might be helpful for this. It stores an encrypted directory in the cloud but mounts the decrypted contents locally on your hard drive so you can work with them. I'm still looking into it myself but it appears to have been designed to let people use cloud storage without ever revealing the contents to the provider.

See https://github.com/cryfs/cryfs/issues/335

CryFS - Intended to replace eCryptfs and fscrypt (which you can also look at if CryFS doesn't work for you) and add improvements. Unlike LUKS and veracrypt, you don't have to allocate the space in advance; as you add more data it just has more files containing the encrypted data. It is also intended to work with cloud sync things like Dropbox. So I expect you should also be able to store it in an NFS or samba share and then mount it so the encryption happens locally and the server never sees the unencrypted data. If you use KDE, the "vaults" program provides a good UI. Details at https://www.cryfs.org/

Instead of large containers, perhaps use something like CryFS so the uploads are not as large? See https://www.cryfs.org/

Exemplo: https://www.cryfs.org/

OR to attempt to recover data from the old drive, you can use a USB and boot into a Linux Live instance, install apfs-fuse to mount the partition if it is not encrypted. Here's a tutorial to boot into Ubuntu Live. And here is a link to the github repository for apfs-fuse.

There is a WIP Linux fuse based driver on GITHUB (here).

Also potentially useful: apfs-fuse and apfsprogs.

PS: there's apparently an apfs-fuse module out there (read-only though) if you want to copy files from OSX to Linux, although I know nothing about how reliable it is.

i'd try booting a live linux environment and using apfs-fuse , easiest with an arch based distro, recommend manjaro and using AUR to install it.

Assuming you're running High Sierra or later, though, reading the drive on anything other than macOS is gonna take a bit of know-how, because it'll be APFS-formatted, and there just isn't much support for APFS on other platforms currently. You'll need to run Linux and compile apfs-fuse in order to mount the drive.

If the SSD is soldered to the logic board you might be screwed since you can't boot into Target Mode. However, for what it's worth, I yanked the SSD out of an older MBP that tanked and successfully mounted it as read-only on my Linux machine via apfs-fuse. This despite the fact that my wife's 2019 MBA with Big Sur couldn't mount or fix it.