Cryptonite can't see EncFS encripted files

[HacKanCuBa]

This happens always: try to open an encrypted foldes with(out) files in it, and it will always say that can't find the .xml descryptor. It happened on an EncFS done on my Ubuntu 14.04 workstation, and the same on the one made by Cryptonite. Both on paranoid mode. I bypass the issue by manually selecting the .xml descriptor. Then the folder is correctly decypted. Here are some screenshots: https://www.dropbox.com/sh/bxh4kcy6cvv7dp6/AAC_HPMfBdsEF1M0G5gpEdjja/Cryptonite?dl=0

As you can see, the folder is correctly populated. On my workstation, either through command line or through gnome-encfs-manager, everything works fine.

Here's the content of the .xml:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE boost_serialization>
<boost_serialization signature="serialization::archive" version="10">
<cfg class_id="0" tracking_level="0" version="20">
    <version>20100713</version>
    <creator>EncFS 1.7.4</creator>
    <cipherAlg class_id="1" tracking_level="0" version="0">
        <name>ssl/aes</name>
        <major>3</major>
        <minor>0</minor>
    </cipherAlg>
    <nameAlg>
        <name>nameio/block</name>
        <major>3</major>
        <minor>0</minor>
    </nameAlg>
    <keySize>256</keySize>
    <blockSize>1024</blockSize>
    <uniqueIV>1</uniqueIV>
    <chainedNameIV>1</chainedNameIV>
    <externalIVChaining>1</externalIVChaining>
    <blockMACBytes>8</blockMACBytes>
    <blockMACRandBytes>0</blockMACRandBytes>
    <allowHoles>1</allowHoles>
    <encodedKeySize>52</encodedKeySize>
    <encodedKeyData>
[ERASED]
        </encodedKeyData>
    <saltLen>20</saltLen>
    <saltData>
[ERASED]
    </saltData>
    <kdfIterations>1281552</kdfIterations>
    <desiredKDFDuration>3000</desiredKDFDuration>
</cfg>
</boost_serialization>

Created by Cryptonite itself.

I'm using Cryptonite on Android 4.1 Samsung Galaxy S3 rooted. And EncFS v1.7.4 on Ubuntu 14.04.2 if it matters, which I doubt.

Awesome soft, let me know how can I help you more :D

Cheers!

[HacKanCuBa]

I tried removing the link with Dropbox, and then re-linking. Nothing changes.

[neurodroid]

On some systems, Cryptonite appears to ignore dot files, which is particularly problematic because the configuration file is a dot file. Unfortunately I haven't been able to figure out the reason yet (it's not reproducible on my test systems).

[HacKanCuBa]

I thought that, but if you check the pic, u will notice that Cryptonite doesn't see ANY file on the encrypted folder! That's weird. So, one of the very first thinhs i tried was coping the .xml but renamed, in the same folder. Didn't work because it can't see any file. So then i downloaded the xml to my sd card, and that worked perfectly! Both with and without the beginning dot. There has to be something funny in the detection routine... perhaps make it able to show every file? How else can i help u? Im a web dev, and have dev with c and c++ in the past. Dunno much about android unfortunately. Cheers!

[HacKanCuBa]

Saving as default doesn't work either: it fails quickly with "wrong password" (when it's not wrong...)

[neurodroid]

@HacKanCuBa Can you check if v0.7.17 fixes this issue?

[HacKanCuBa]

Unfortunately, nothing changed regarding this issue :( I'm checking it once more as we speak, but the same: I have to use a local xml file for this to work... As a regression, for some reason now it doesn't hold my Dropbox account link, so everytime I open the App I need to "Link w/ Dropbox" again xD

[ArtHoff]

Hi I'm seeing the same symptoms (no files are visible and the "Couldn't find an EncFS configuration file..." message pops up when trying to decrypt the repository on Dropbox. This only happens with the Dropbox repositories I created from my windows client (EncFSMP). If I use Cryptonite on my S7 Edge to create the repository I can see it and access it both via EncFSMP and Cryptonite.