Access to keepass db in shared pCloud folder

[CrfzdPQM6]

It seems that Keepass2Android can only access a database in pCloud if:

1. it is in the path /Applications/Keepass2Android, AND
2. that Keepass2Android folder is owned by the pCloud account on the device

(2) effectively blocks sharing a folder between two pCloud users as far as Keepass2Android functionality is concerned.

Have I misunderstood? When I try to setup access to the folder with Keepass2Android on the second account, Kp2A just creates a new folder in /Applications/, ignoring the existing one called "Keepass2Android" but owned by someone else. Is sharing possible?

[PhilippC]

I'm not sure if this is possible with the Java SDK of pCloud. I created https://github.com/pCloud/pcloud-sdk-java/issues/33 to clarify this.

[CrfzdPQM6]

Thanks, @PhilippC , let's see if they reply (I see the reply-time is a couple of weeks sometimes). If not, I guess that excludes keepass db sharing on android devices, using pCloud. Would be happy not to have to revert to google... :(

[CrfzdPQM6]

Sounds like they fixed it! Fast work!

[PhilippC]

currently blocked by https://github.com/pCloud/pcloud-sdk-java/issues/34

[CrfzdPQM6]

Yes, I see. Thanks for trying the implementation so fast :)

[CrfzdPQM6]

Any luck with getting a release out that implements this?

Thanks for all your work on this so far.

[user-elly]

I can also confirm this problem when trying to work with a keepass file that is shared by another account. (My workaround is currently to create a copy into the right folder by a script running in my PC. Just to have any old copy readable in case of emergency....)

But i would like to add another aspect if this functionality will be improved: Please allow to use any pathname to configure. On other platforms i use a more hidden place that obfuscates the purpose of the database file. The file itself appears in my case also as any harmless office document. I like it to give no hint to any intruders where to look for my secrets. The hard coded root folder in pCloud indicates directly where to search for relevant files. The encryption is already strong. But hiding is additional safety. A second reason for flexible folder names in pCloud is the ability to use shared keepass databases. When i use keepass in pCloud it is not possible to access another keepass file that has been shared with me. When i use the defined folder name it conflicts with my personal keepass folder. Its not possible to distinguish shared and own folder by different names. I mean for example when within a family you use your personal keepass database and one another shared with the whole family or partner. So the fixed name gives limitations here.

[user-elly]

Any luck with getting a release out that implements this?

Here was no repsonse posted. So i tried myself the latest beta channel version (1.09d-r0). Apparently it still does not work with a shared applications folder. I do get in parallel a new empty "Applications (2)" folder. And this is no longer shared on pCloud as it was meant to be. I mean.... use it back and forth synchronized.

Is there any release planned with this feature? Would be relly helpful when somone is working in pCloud environments.

[user-elly]

Using version 1.10:

• It is possible to access now any folder in pCloud. Thats very helpful. Thanks for that!
• but when i try to access any folder that has another pCloud user shared with me then it does not work. The shared folder is shown as empty. No files and no subfolders are displayed when i try to open/select an existing database there.

[PhilippC]

@user-elly I updated pCloud SDK last weeks which fixes this, but there is no release with that feature yet