Mounted but no data #384
Comments
|
Looks like the password is incorrect, there's no fixing that: |
|
Thank you for the reply. The password was part of the issue. My password contains a ';' semi-colon.
However, So where are the 9 entries? |
|
To what did you set |
|
The file in /home/jack/Dropbox/.enc is an old version.
ENCFS6_CONFIG is set to /home/jack/.keychain/encfs6.xml
…-----Original Message-----
From: Ben RUBSON <[email protected]>
Reply-to: vgough/encfs
<reply+008ddae32db2b40155638c1634a7c5890bab7d41fcc6387892cf0000000115a8
[email protected]>
To: vgough/encfs <[email protected]>
Cc: jakoch5876 <[email protected]>, Author <[email protected].
com>
Subject: Re: [vgough/encfs] Mounted but no data (#384)
Date: Sun, 13 Aug 2017 12:20:10 +0000 (UTC)
To what did you set ENCFS6_CONFIG ?
You have a .encfs6.xml file in /home/jack/Dropbox/.enc so you should
point to it (or unset ENCFS6_CONFIG).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
If the new conf file is a whole new one (not just a password update from the old conf file), and if your data files were created with the old conf file, you won't be able to decode them with the new Perhaps you are also facing #343. |
|
The system had been working with the new xml file. The password and file were set up years ago. The old xml file does not work.
Also using the --forcedecode flag makes no difference.
I will read through #343.
Sent from TypeApp
…On Aug 13, 2017, 8:50 AM, at 8:50 AM, Ben RUBSON ***@***.***> wrote:
If the new conf file is a whole new one (not just a password update
from the old conf file), and if your data files were created with the
old conf file, you won't be able to decode them with the new
`encfs6.xml` file, even if you used same password for both.
You will then have to use the old `encfs6.xml` file.
Perhaps you are also facing #343.
You would then have to update to EncFS 1.9.2.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#384 (comment)
|
|
Ok Just read through #343. I am also running Arch Linux. I will try the fixes suggested.
Thank you
Sent from TypeApp
…On Aug 13, 2017, 9:13 AM, at 9:13 AM, John Koch ***@***.***> wrote:
The system had been working with the new xml file. The password and
file were set up years ago. The old xml file does not work.
Also using the --forcedecode flag makes no difference.
I will read through #343.
Sent from TypeApp
On Aug 13, 2017, 8:50 AM, at 8:50 AM, Ben RUBSON
***@***.***> wrote:
>If the new conf file is a whole new one (not just a password update
>from the old conf file), and if your data files were created with the
>old conf file, you won't be able to decode them with the new
>`encfs6.xml` file, even if you used same password for both.
>You will then have to use the old `encfs6.xml` file.
>
>Perhaps you are also facing #343.
>You would then have to update to EncFS 1.9.2.
>
>--
>You are receiving this because you authored the thread.
>Reply to this email directly or view it on GitHub:
>#384 (comment)
|
|
My xml file already had 0s and 1s.
I can create new files that are readable.
I also tried the precompiled version. Also tried rolling back encfs and tinyxml2. No change.
Not sure what else to try.
Sent from TypeApp
…On Aug 13, 2017, 9:28 AM, at 9:28 AM, John Koch ***@***.***> wrote:
Ok Just read through #343. I am also running Arch Linux. I will try
the fixes suggested.
Thank you
Sent from TypeApp
On Aug 13, 2017, 9:13 AM, at 9:13 AM, John Koch
***@***.***> wrote:
>The system had been working with the new xml file. The password and
>file were set up years ago. The old xml file does not work.
>
>Also using the --forcedecode flag makes no difference.
>
>I will read through #343.
>
>Sent from TypeApp
>
>On Aug 13, 2017, 8:50 AM, at 8:50 AM, Ben RUBSON
***@***.***> wrote:
>>If the new conf file is a whole new one (not just a password update
>>from the old conf file), and if your data files were created with the
>>old conf file, you won't be able to decode them with the new
>>`encfs6.xml` file, even if you used same password for both.
>>You will then have to use the old `encfs6.xml` file.
>>
>>Perhaps you are also facing #343.
>>You would then have to update to EncFS 1.9.2.
>>
>>--
>>You are receiving this because you authored the thread.
>>Reply to this email directly or view it on GitHub:
>>#384 (comment)
|
|
The current Arch packages are encfs 1.9.2-1 and tinyxml2 5.0.1-1.
So I did not build.
…-----Original Message-----
From: Ben RUBSON <[email protected]>
Reply-to: vgough/encfs
<reply+008ddae3907a04d405244b7c0d03d88c6595e9e73287f01892cf0000000115a8
[email protected]>
To: vgough/encfs <[email protected]>
Cc: jakoch5876 <[email protected]>, Author <[email protected].
com>
Subject: Re: [vgough/encfs] Mounted but no data (#384)
Date: Sun, 13 Aug 2017 09:31:13 -0700
Did you try building EncFS 1.9.2 ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
@jakoch5876 If this is correct it is unlikely that you are affected by #343, confirmed by the fact that you already have 0 and 1 for the booleans. Can you post the whole encfs6.xml, minus the |
|
Here is the xml file. |
|
Another occurence of a Dropbox issue : #388 |
Closed
|
Could you please give us the result of the following command ? Then, try to copy the This could tell us whether or not Dropbox makes EncFS behave badly. Thx 👍 |
|
Mmmmh the copy test may not work if DropBox copies files from its cache... |
|
Sorry for the delay.
$ ls -l /home/jack/Dropbox/.enc/
total 3412
drwx------ 4 jack users 4096 Aug 13 09:59 0j,LHprpZSamA8WQKODsCyx7
drwxr-xr-x 5 jack users 4096 Apr 9 17:54 7Zdg3PkOouqW5xhGO1XIbkZS
-rw-r--r-- 1 jack users 13432 Jun 23 14:59 8N0tr8dQTOJHVevU,qe9LTgWUbIkTb-H8uIo-CteLCnha1
-rw-r--r-- 1 jack users 132642 Jun 17 13:36 9HBIiToRwErBtzI5zuNdlKkc0x,5,GMOh-Llyyg5J7te4jKNOCBBi083Ndnn2Q7PyO1
drwxr-xr-x 5 jack users 4096 Jan 28 2017 ABLyw7iD9LD5d9JmDKifbSwy
drwxr-xr-x 5 jack users 4096 Sep 23 2016 ASIJ-2iU1oKAHQWCzlD9VoJB
-rw-r--r-- 1 jack users 11368 Jun 23 15:06 BIFP1hWXuSLS8pDmlfiZ6XH1KdZfLZIu15xkd-BhpgxbG,
-rw-r--r-- 1 jack users 287792 Jun 1 09:57 CrmnHw5ABmfaUeu9asIAGZvJdubDKcqM1oNTRS3PHhDrf1
-rw-r--r-- 1 jack users 287800 May 14 10:54 CzC3UjGKAAXG3iQtG9MPjPHCHYofK9fyPVK6pMhcw7dpG,
drwxr-xr-x 2 jack users 4096 Sep 24 2014 EBufSuDd2-BtllczyiDb3opF
-rw-r--r-- 1 jack users 101818 Jun 17 14:00 fkV3vysEDsEhC7IqkSPTH2Qo3uyUh0f2Gre5PrxrXx2wEHPRwXkn4HYp1VeMMNfVDpD
-rw-r--r-- 1 jack users 12400 Jun 22 20:45 Hn1iai9,cJqsgNLnLIgB0YpA,OuGVCUagXlJ4dnqEv5Ob-
-rw-r--r-- 1 jack users 125816 Mar 6 2015 Lhst6SbxfC6UMCyBuXHasL9gHJkcN-8G81Rx6RGSaPID2OImqH6fGtTCpa-g4bpbBu0
-rw-r--r-- 1 jack users 287794 May 14 10:37 mHr35JnjBLKzEKcD4qFaOdzyIITjtumLY48b5unjTgsRR,
drwxr-xr-x 4 jack users 4096 Jun 23 15:00 r64tBEDNHvyttYflpNUFXLyU
-rw-r--r-- 1 jack users 287801 Jun 1 09:57 -UYFtf0DYCKay2go8lu557rl
-rw-rw-r-- 1 jack users 230738 Feb 19 2017 '-UYFtf0DYCKay2go8lu557rl (Appenzeller'\''s conflicted copy 2017-02-21)'
-rw-r--r-- 1 jack users 250680 May 6 17:13 wlBz7SXH-Yce5Cw8ZtY6ZQwMMazvdfEieiK5hMIjeEQeH0
-rw-r--r-- 1 jack users 287713 May 14 10:25 x49g,pTYDANQ6tDJcSv28hlvhaQaf5Td5JVjTfcDyjJs8,
drwxr-xr-x 3 jack users 4096 Sep 23 2016 x,AI9TYYIWukPDQuIegOqQKv
-rw-r--r-- 1 jack users 14243 Jun 22 20:45 xAxvkhTNhxt9GPGoobwaR,JsqnSVCBKELTBFX9JN9U2qD,
-rw-r--r-- 1 jack users 761672 Jun 17 13:58 YPlmYuhteZqz,FYZj7FnX4L3laraO0txqRY-Y43NIMh1z1
drwxr-xr-x 10 jack users 4096 May 20 07:09 zkS-ASPbXjTtpLlvk7j-r5Lm
-rw-r--r-- 1 jack users 230681 Mar 6 2015 zqD4Axo6nWm3NwOl5V335sV-fmKPEc9kqICHMgsbfEr
$ ls -lR /home/jack/Dropbox/.dropbox.cache/
/home/jack/Dropbox/.dropbox.cache/:
total 4
drwxr-xr-x 2 jack users 4096 Jun 27 10:32 prefetch_cache
/home/jack/Dropbox/.dropbox.cache/prefetch_cache:
total 0
After the mount :
$ ls -lR /tmp/local_encfs
/tmp/local_encfs:
total 0
|
|
OK thx. |
|
Two computers have access the EncFS. |
|
Did you try to access it from the other machine these days to see if ever it could work ? |
|
Unfortunately the exact same situation. |
|
For sure you also tested to show hidden files |
|
This time from the laptop |
|
Ok I have read this top to bottom again. You have two computers that sync encrypted files via Dropbox. The encfs config file is NOT synced via Dropbox. Now both computers cannot decrypt the encrypted files. The question is, how can this problem spread from one computer to the other? There must be some detail missing here. |
|
@jakoch5876 are you sure you did not mess-up your encfs config file bringing it between your 2 computers ? |
|
No it had been working between the two computers for over a year.
I think something happened when I had both machines accessing the file system at
the same time.
…-----Original Message-----
From: Ben RUBSON <[email protected]>
Reply-to: vgough/encfs
<reply+008ddae3855793319b07f9c9940f71c82b74d691491091bf92cf0000000115f9fa1a92a16
[email protected]>
To: vgough/encfs <[email protected]>
Cc: jakoch5876 <[email protected]>, Mention <[email protected]>
Subject: Re: [vgough/encfs] Mounted but no data (#384)
Date: Sat, 14 Oct 2017 09:15:22 -0700
@jakoch5876 are you sure you did not mess-up your encfs config file bringing it
between your 2 computers ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Could we close this ? |
|
Closing this for now then... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there any way to force a mount when receiving a checksum mismatch: expected 1504336836, got 1627605868 [SSL_Cipher.cpp:541] error? After a reboot the system will not mount. Absolutely no idea what caused the corruption.
The full output of encfs -v is:
There are 24 entries in the .enc directory.
Any attempt at
$ encfsctl decodeproduces the following output.
2017-08-12 09:38:18,748 ERROR decode err: invalid padding sizeThe text was updated successfully, but these errors were encountered: