can't mount files created by cryptkeeper

Thank you for your question.

Does your stash contain the file ".encfs6.xml"? And what do you mean exactly by elaborate setup? GEncfsM does some simple checks on the stashes to at least make sure that they look alright before making them accessible. Eventually there is some conflict there.

What do you mean by standard gnome and gnome flashback? The icon should sit in the notification bar which is accessible by pressing windows-key+M. If it does not, could you please post the contents of the environment variable DESKTOP_SESSION?

Regards,
Moritz

Moritz, thanks much for the fast reply!

>Does your stash contain the file ".encfs6.xml"?

No, just binary file .encfs5

> And what do you mean exactly by elaborate setup?

Various back up programs are looking at the stash and various editors work with files in the mounted directory. None was running during testing.

> What do you mean by standard gnome and gnome flashback?

When you login, gnome usually gives you a choice whether to log in to standard Gnome (3.10.4-0ubuntu5.2 in my case) or Flashback (f.k.a. Fallback) with either Compiz or Metacity, which looks like Gnome 2 and is way more robust - from what I understand it's like a failsafe mode for Gnome. But that probably doesn't matter here (see below).

>The icon should sit in the notification bar which is accessible by pressing windows-key+M

The icon is there - I just didn't know about windows-key+M (just upgraded from Gnome 2 yesterday). I used that new knowlege to do some more tests and GEncfsM behaves exactly the same in Classic and Flashback - sorry about the confusion!

Very old stashes with .encfs5 config files are not supported.
See https://bugs.launchpad.net/gencfsm/+bug/1127068

I added some experimental support in trunk but I can't test it due to the lack of these old stashes. If you feel brave you can install the corresponding package and report back. (Don' forget to make a backup first)
[amd64] https://code.launchpad.net/~gencfsm/+archive/ubuntu/trunk/+files/gnome-encfs-manager_1.8.12.1%7E523%7Eubuntu14.04.1_amd64.deb
[i386] https://code.launchpad.net/~gencfsm/+archive/ubuntu/trunk/+files/gnome-encfs-manager_1.8.12.1%7E523%7Eubuntu14.04.1_i386.deb

Close GEncfsM and execute the following command in a terminal
gnome-encfs-manager --reset

Regards,
Moritz

Btw., you probably mean the Gnome Classic mode. We had a Fallback-mode until 3.8 which indeed used metacity but the Classic mode is simply the gnome-shell ("normal" Gnome 3) with a more traditional interface. Technically they are the same (they are based on Mutter as window manager / compositor)

Thanks!

I tried i386 package but it didn't change anything. I'll be happy to test it some more for you if you think it's worth the time.

For my purposes it's probably easier just to get cryptkeeper to work one more time somehow and re-encrypt the whole thing with GEncfsM.

Best regards,

Thanks for testing.
Was the config file correctly detected? The variable "encfs_config_file" should be set to ".encfs5" inside the advanced stash configuration dialog.

Could you please post the output of
gnome-encfs-manager --checkstash ~/path/to/the/stash

My guess would be that the validation check fails.

I set up the variable to ".encfs5", quit GEncfsM, did

gnome-encfs-manager --reset

and started GEncfsM. It asked for the password and mounted the old crytkeeper's directory. So far looks like everything works and I can mount and unmount it without any problems.

Just in case you still need the output:

leon@box12:~$ gnome-encfs-manager --checkstash ~/path/to/the/stash

Stash directory exists and is a folder ... yes
drwx------ 6 leon leon 4096 Aug 25 13:58 /path/to/the/stash

Encfs config file exists ... yes (.encfs5)
Encfs config file is readable ... yes
Encfs config file looks valid ... yes
-rw-r--r-- 1 leon leon 239 Apr 11 2007 /path/to/the/stash/.encfs5

leon@box12:~$

I noticed that GEncfsM did not create .encfs6.xml - is there a way to convert my old type stash to the new one? Otherwise, I suspect it's only a matter of time before it stops working after an updgrade ...

Thanks,

Thanks!

Thanks Moritz Molch, that solved my question.