[Borgbackup] impossible to mount encrypted repository (via fuse)

[Thomas Waldmann]

David, you have to get a deeper understanding about what encryption
mechanisms you use on your system and how they work.

Just look at the configs, read docs about what ecryptfs is and how it
works, read about full disk encryption on linux (usually dm-crypt, LUKS).

Your current assumption seems wrong as far as I can tell:

- you are using ecryptfs, obviously ("home directory encryption" in
ubuntu) - this is where the strange dir and file names come from.

- you are either not using full disk encryption (dm-crypt), or

- even if you do, it is not relevant for the current case as with
dm-crypt you never see such strange dir and file names. either you have
the device "opened", then you have a decrypted device mapper device and
everything looks normal/decrypted when using that.

Using ecryptfs additionally to dm-crypt might not make sense for a lot
of scenarios. Only do that if you positively know why you need that.

If you start from wrong assumptions, you might get more and more into
even more strange to bizarre assumptions about how your system (or borg)
works. I'ld guess it is way simpler than you currently think it is.

While borg is far more advanced than rsync, in the end both are just
reading files via the normal file reading functions. No magic.

So, you likely just backed up ecryptfs' encrypted backend files and you
maybe rather wanted to backup the (decrypted) files inside the mounted
ecryptfs.

BTW, i'ld like to note that configuring disk / fs encryption is not
on-topic on this list, so if you (after reading the docs) have more
questions about that, maybe ask on a list or forum where it is on topic.

-- 

GPG ID: 9F88FB52FAF7B393
GPG FP: 6D5B EF9A DD20 7580 5747 B70F 9F88 FB52 FAF7 B393