Steps to reproduce

Steps to reproduce the behavior:

1. Go to default screen while vault is unlocked
2. Click on the lock button
3. See error

Current behavior

Lock closes, but the actual directory doesn't unmount. When I open the mount directory, I can still see all the files.

Expected behavior

Mount directory should be emptied, same way as when using the fusermount -u command

Version information

• Application: 0.3.0
• Gocryptfs (if related): v2.3
• Distribution: Fedora 36

Steps to reproduce

Steps to reproduce the behavior:

1. Open file picker either from preferences or import menu
2. Try to resize the window

Current behavior

Can't resize file picker window

Version information

• Application: 0.2.0
• CryFS (if related): I do not install CryFS because theres no such package in fedora rpm repo
• Gocryptfs (if related): 1.8.0
• Distribution: Fedora 35

Additional information

https://user-images.githubusercontent.com/18339774/147463736-f9ae39fe-489c-4908-9c08-ce2071f2616d.mp4

Situation: My Linux partition was basically bricked a few days ago. All files intact, and I accessed them from new Linux partition, including vaults files.

• I placed the (gocryptfs) vault files into the correct place, all files intact. (home/name/.var/app/io.github.mpobaschnig.Vaults)
• Downloaded and installed gocryptfs back-end.
• I have the correct password to open the files.
• The "unlock" icon on Vaults lights up. I press it, enter my password, and the error "The encrypted data directory is not empty" appears.

I hope I came to ask at the right place. What does this error mean? and how to solve it?

Vaults can't find CryFS backend.

My setup: Fedora Silverblue 36, latest Vaults from Flathub stable, cryfs-0.11.2-1.fc36.

$ rpm -qi cryfs
Name        : cryfs
Version     : 0.11.2
Release     : 1.fc36
Architecture: x86_64
Install Date: Tue 10 May 2022 18:57:10 MSK
Group       : Unspecified
Size        : 4499524
License     : LGPLv3
Signature   : RSA/SHA256, Sun 27 Mar 2022 13:36:24 MSK, Key ID 999f7cbf38ab71f4
Source RPM  : cryfs-0.11.2-1.fc36.src.rpm
Build Date  : Sun 27 Mar 2022 13:05:17 MSK
Build Host  : buildvm-x86-27.iad2.fedoraproject.org
Packager    : Fedora Project
Vendor      : Fedora Project
URL         : https://www.cryfs.org/
Bug URL     : https://bugz.fedoraproject.org/cryfs
Summary     : Cryptographic filesystem for the cloud
Description :
CryFS provides a FUSE-based mount that encrypts file contents, file
sizes, metadata and directory structure. It uses encrypted same-size
blocks to store both the files themselves and the blocks' relations
to one another. These blocks are stored as individual files in the
base directory, which can then be synchronized to remote storage
(using an external tool)

Steps to reproduce

Steps to reproduce the behavior:

1. Go to 'Import vault'
2. Select directory
3. Click next
4. See error

Current behavior

Installed backend not detected when importing an already made vault. While creating and using new one works.

Expected behavior

Installed backend should be detected when importing vault.

Version information

• Application:0.2.0
• CryFS (if related):
• Gocryptfs (if related):
• Distribution:Fedora Silverblue

Additional information

New vault Import vault

Steps to reproduce

Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Current behavior

A clear and concise description of the current behavior.

Expected behavior

A clear and concise description of what you expected to happen.

Version information

• Application:
• CryFS (if related):
• Gocryptfs (if related):
• Distribution:

Additional information

Please provide the terminal output when the bug happens and if applicable, add screenshots or screencasts to help explain your problem.

This isn't so much a bug I'd guess, as opposed to just the way things are in Linux with Flatpaks installed as User, AFAIK. As an experiment, I installed Vaults via Flathub as User to my Home folder, then I made a vault using CryFS. Then I simply arbitrarily changed all permissions of everything in Home, as for example, via chmod + read, write, & executable. The result was that Vaults no longer respected their passwords, even if I changed permissions of the flatpak folders (local and var) back to my best guess as to their defaults. This is all somewhat expected, but I thought I should report here how easy it seems to nuke vaults, unless there is some vital piece of information I'm missing in order to restore them after their flatpak contents' permissions are changed via even GNOME Shell File Properties. This was just an experiment; I had no important data in them. But I conclude if somebody was trying to keep important documents or whatever, they should know it seems very easy to destroy access to them with a simple command or GUI gesture, and I'm not sure it's possible to recover. I don't know how the encryption works, but I'm guessing any modification to file permissions ruins a key or config in the app directory? Therefore, I suppose it should be noted somewhere that Vaults ought to be installed as a System Flatpak to reduce the chances of this happening so easily. I didn't see it if it already is. I don't know. Or maybe somebody here knows how to recover after a weird, but simple scenario like this.

Anyway, thanks for this neat app. I like it.

Steps to reproduce the behavior:

1. Arbitrarily change permissions of Vault flatpak folders back and forth.
2. Try to re-enter a vault. Password will fail.

• Application:
• CryFS
• Vault Flatpak (user install)
• Distribution: Fedora 36

Steps to reproduce

Steps to reproduce the behavior:

1. Create new vault
2. Open file chooser to set either mount or data directory
3. Navigate into an existing empty folder you want to choose as directory

Current behavior

When in an empty directory in the file chooser, it is not possible to "select" the folder (button is greyed out). one needs to navigate one level up, mark the folder and can now click the select button

Expected behavior

When in an empty folder, it should be assumed that I could want to select the current directory as destination, and be offered to click the select button (or confirm via return-key)

Version information

• Application: 0.3.0 (flatpak)
• Distribution: Debian unstable

Is your feature request related to a problem? Please describe. On smaller screens (e.g. pinephone and the librem 5) it would be easier to use the configuration dialogs if they took up the whole screen.

Describe the solution you'd like Windows should take up the full vertical space on small screens.

Additional context Possible resources: libadwaita and examples of adaptive menus in other projects like clapper.

Images Note: These were take on the mobile QEMU image of PureOS

A small PR that makes three more strings translatable, namely:

• the Vault Settings window title when editing vaults
• the short descriptions of gocryptfs and CryFS, which show up when creating a new vault

Furthermore I updated the German translation with these added strings.

I deleted the two old references to src/ui/pages/start_page.rs and src/ui/pages/vaults_page.rs. Both files were already removed a while back in 61c8441a84245cb3ba1187322acaae6593eeafe1. I also reordered the # src/-part, so that it's arranged like the rest of the list for better readability.

Is your feature request related to a problem? Please describe. I'd like to be able to mount multiple different encrypted directories without having to keep empty mount directories around.

Describe the solution you'd like Select a parent directory where mount directories would be automatically created with (partially random?) generated directory names.

Additional context e.g. I choose the parent directory /run/media/teohhanhui, and Vaults would generate /run/media/teohhanhui/Vaults-{uuid}

gocryptfs in their documentation mention: The old principle still applies: Important data should have a backup. Also, keep a copy of your master key (printed on mount) in a safe place. This allows you to access the data even if the gocryptfs.conf config file is damaged or you lose the password.

That's why I think it is important to warn user how important gocryptfs.conf is and tell them to back it up. So that when bitrot happens on the config files or user accidentally delete it they can use the backed up conf.

Also I think having an unencrypted version of file as a backup is defeating the purpose of file encryption.

Describe the solution you'd like Display a warning message after making a vault

This PR includes gocryptfs and CryFS into the flatpak.

Draft until these issues are solved:

CryFS:

• [ ] Build from source
• [x] init works
• [x] open/mount works
• [x] close/unmount works

gocryptfs:

• [ ] Build from source
• [x] init works
• [ ] open/mount works
• [x] close/unmount works

Closes: https://github.com/mpobaschnig/Vaults/issues/8

First of all, thank you for your amazing work. I was using a script in nautilus with zenity to open my vault and even tried to build a gnome extension for it, although, I am not a developer. Thank you.

May I suggest to include your project on the GNOME Circle. The project will benefit from more advertising and visibility, and hopefully also from contributions.

Is your feature request related to a problem? Please describe. On distros like fedora silverblue you generally are discouraged from layering packages.

Describe the solution you'd like Include gocryptfs, CryFS, libfuse in the flatpak.

Additional context Considering these are sensitive deps I wouldn't want them included in the flatpak unless there was a way to have a flathub bot watch upstream for updates and make automatic PRs.