search

keepassxreboot / keepassxc

KeePassXC is a cross-platform community-driven port of the Windows application “Keepass Password Safe”.
https://keepassxc.org/
Other
20.01k stars 1.42k forks source link

Cannot open database files located under symlink / \Device\Volume mount point anymore #10977

Closed b1t-hunter closed 1 week ago

b1t-hunter commented 1 week ago

Overview

I am using Cryptomator for sharing my kdbx with multiple machines. On Windows, Cryptomator uses symbolic links to mount the encrypted container into the filesystem. I could previously access this file without problems with KeePassXC (2.7.8), but it stopped working in the newest version (2.7.9), telling me that the selected path is not safe to use.

I get an error (in German) when I want to select the symlink leading into my container with kdbx file.

Error

This roughly translates to: 

Selected path is not available:

Cannot access path at D:\XYZ.

The selected path cannot be followed, because it contains a non-trustworthy mount point.

I have other symlinks on my system that can be followed without problems. So, I assume the problem is not in the symlink, but the actual mount point that Cryptomator provides and the symlink is pointing to. It has the form of "\Device\Volume{SOME-GUID}\".

Steps to Reproduce

  1. Put the kdbx file into an FS-mounted share of Cryptomator.
  2. Select the "Open Database" and try to locate your file.
  3. When trying to enter the container over the symlink, the error occurs.

Expected Behavior

As in earlier versions, you should be able to select databases in Cryptomator shares, i.e., files in an "anonymously" mounted drive.

Actual Behavior

An error occurs, telling me that the source is not trusted.

Context

KeePassXC - Version 2.7.9 Revision: 8f6dd13 Operating System: Windows 11

b1t-hunter commented 1 week ago

I reverted back to the previous version and it started working again.

droidmonkey commented 1 week ago

This is a windows issue. You will need to either install KeePassXC or place the portable version in the same network share. This isn't on our side.

droidmonkey commented 1 week ago

See https://github.com/keepassxreboot/keepassxc/issues/9937

b1t-hunter commented 1 week ago

This worked in the previous version, though, without installing KeePassXC on the share.

droidmonkey commented 1 week ago

It's not an error from keepassxc, is all I can offer. That is a Microsoft error.