Hi there,
I need some help in untying a knot in my head. I am not a regular user
of the encryption feature.
I understand that EncFS somehow scramble/hash all names of files and
directories.
BIT offers a "decode" feature to make the log file readable and convert
the scrambled paths into there original names.
What I do not understand is that this decode (a checkbox in the bottom
of the Log View dialog) is offered only for SSH-Encfs profiles but not
for local-Encfs.
When viewing the log for a local-Encfs backup the paths are already
human readable in not scrambled. But in the filesystem the paths are
scrambled.
It seems that decoding is already done in local-Encfs but not in
SSH-Encfs. Why?
Is there a good reason to have that separated behavior?
Thanks
Christian
_______________________________________________
Bit-dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3//lists/bit-dev.python.org
Member address: [email protected]
