Can't mount existing filesystem on M1 mac

[adamlamar]

I have an existing encfs filesystem created on an intel mac several years ago. I am able to mount this filesystem on the intel mac with no issue.

When mounting the same filesystem (via dropbox) to an M1 mac, I am no longer able to mount:

Error decoding volume key, password incorrect

I know the password is correct.

Conversely, with an encfs filesystem created on the M1 mac, the same error is seen when mounting on the intel mac.

Version: 1.9.5

[Keisial]

What are the filesystem settings? Are you able to decode it with encfsctl?
Could it be an encoding problem of the password?

[adamlamar]

Well this is embarrassing. I tried it opening up my old encfs and it works now. I can also decode with encfsctl:

encfsctl ~/Dropbox/BoxCryptor.bc

Version 6 configuration; created by BoxCryptor for iOS 1.3.3 (revision 20100713)
Filesystem cipher: "ssl/aes", version 3:0:0 (using 3:0:2)
Filename encoding: "nameio/null", version 1:0:0
Key Size: 256 bits
Using PBKDF2, with 5000 iterations
Salt Size: 160 bits
Block Size: 4096 bytes
File holes passed through to ciphertext.

Previously I had reproduced the problem with brand new encfses as well, where M1 couldn't read intel and intel couldn't read M1. But they could read their own respective encfs.

In any case it looks fixed now!