Keepassxc: USB/Removable Drive Access

Created on 15 Mar 2017  ยท  14Comments  ยท  Source: keepassxreboot/keepassxc

i feel like i am just missing something really obvious here...but i cant seem to find it :(

Expected Behavior

Open a db or key file from an external removable usb drive

Current Behavior

When i try to open a db for key file from a usb drive, i cannot see the drive, i am restricted to my home folder only.

Possible Solution

Steps to Reproduce (for bugs)

  1. Attach usb drive with key file on it
  2. start keepassxc
  3. Click 'browse' (for key file)
  4. Cannot see the usb drive that is mounted in /media/username/

Context

Cannot open db file or key file

Your Environment

  • KeePassXC version/commit used: 2.1.3
  • Qt version (e.g. Qt 5.3): 5.6.1
  • Compiler (e.g. Clang++3.6.0): snap 2.23.1
  • Operating System and version: Ubuntu 16.04 LTS 64bit
  • Other

    • my home folder is encrypted (using built in ubuntu feature)

    • i see that snap has a removable-media interface now, but it doesnt seem to be available as a plug for keepassxc

bug distribution

Most helpful comment

OK, the snap has been updated in the store to include the removable-media plug. Since it is NOT auto connected, you have to manually execute the following command after installation to use it:

sudo snap connect keepassxc:removable-media :removable-media

Based on my limited testing it also appears that you need to manually type in /media into the filename entry of the open file window to actually see the drive...

All 14 comments

Try our AppImage and see if it works. Snap packages have dedicated permission management and you might not have the needed permissions to access USB drives.

yes, it does work from the appimage. perhaps you could add the removable-media interface as a plug for the snap package in a future release?

https://github.com/snapcore/snapd/wiki/Interfaces#removable-media

Ugh so many plugs....

This also affects permanently mounted network drives, not just removable USB drives.

I'm just going to inject this into the current 2.1.4 release so that we get it up and running.

OK, the snap has been updated in the store to include the removable-media plug. Since it is NOT auto connected, you have to manually execute the following command after installation to use it:

sudo snap connect keepassxc:removable-media :removable-media

Based on my limited testing it also appears that you need to manually type in /media into the filename entry of the open file window to actually see the drive...

Hi there,
Not sure if my issue is related to this issue, but I can't open any KDBX files on mounted drives in Ubuntu 18.04.01 LTS. I'm trying to open a file on an NFS share somewhere under /mnt.
The Permissions button of Ubuntu Software shows a dialog with three on/off-options, which can be modified but aren't retained after closing and reopening the dialog.
Version is 2.3.4 (snap). There's no issue with the 'apt' version (2.3.1).

Kind regards,
Ralph Hummeling

Did you connect the plug like I mentioned above?

Yes, I did, at no avail.

โฃSent from BlueMail โ€‹

On 17 Sep 2018, 15:27, at 15:27, Jonathan White notifications@github.com wrote:

Did you connect the plug like I mentioned above?

--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/keepassxreboot/keepassxc/issues/400#issuecomment-422016345

I just re-read your comment, the reason this does not work for you is because you mounted it under /mnt. That is not a valid location for snaps. Mount it under /media or /home/[username] to access it.

The snap is installed via Ubuntu Software, the database I'm trying to open is on my NAS, mounted during startup. The mount point is /mnt, as copied from online examples. Didn't encounter any issues with that before.
Just tested with another mount point (under /media as you suggested), and now I'm able to open the database.
Apart from that, the Permissions dialog in Ubuntu Software still doesn't retain its settings.
Thanks for you help so far.

@droidmonkey understood, it's clearly a safety measure. Nonetheless, the user should be notified with some explanation why the app isn't able to access that location.
About the Permissions action in Ubuntu Software, is this beyond the control of this snap?

This is largely a complete failure on Ubuntu's part to clearly articulate the limitations of snaps through the Ubuntu store. Even worse, they are now making snaps and ppa's available side-by-side in the store. This creates much confusion for end users. We already have this documented in our FAQ on our website.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

clementlesne picture clementlesne  ยท  3Comments

bleepnetworks picture bleepnetworks  ยท  3Comments

TheZ3ro picture TheZ3ro  ยท  3Comments

JosephHatfield picture JosephHatfield  ยท  3Comments

mstarke picture mstarke  ยท  3Comments