Could not save database on chromebook/gdrive

[24namnorI]

I installed KeepassDX and keep a shared kdbx file on GDrive (to share the crypt between phone and chromebook). With the database closed on the phone and opened on the chromebook, I cannot make changes. Every change results in "could not save database". KeePassDX version: 2.9.2 (from the playstore) ChromeOS: Version 88.0.4324.22 (Official Build) beta (64-bit)

[thx84]

I have the same issue with my chromebook. I can see the database, but cannot save. If I save from my phone with KeepassDX and reload the database on the chromebook, I can see the new password on the chromebook Running 2.9.12 on both Android and ChromeOS

[samsonluk]

ChromeOS Version 88.0.4324.153 (Official Build) (64-bit) same problems with SMB network file shares in the LAN, can open the database but cannot update it, "could not save database".

[cigno5]

Same here with KeePassDX 3.4.5 and ChromeOS 103.0.5060.132 (Official Build) (64-bit), using kdbx file shared on Google Drive and opened with ChromeOS file manager.

Can do everything with the database but, when saving, "could not save database"

[ghost]

Google Chrome: Version 113.0.5672.46 (Official Build) beta (64-bit) Platform: 15393.27.0 (Official Build) beta-channel brya Channel: beta-channel Firmware Version: Google_Osiris.14505.325.0 ARC Enabled: true ARC: 9899622 Enterprise Enrolled: false Developer Mode: false

EACCES on writing to the file.

[zunixnuz]

Same here... KeePassDX 4.0.5 and latest ChromeOS. EACCES on writing the database on Google Drive. Keepass2Android can handle this situation without problems. Would be great to get a fix for this.

[ghost]

I suspect that Google is displeased with folks transferring a binary encrypted blob around,and also KeePass is a competitor for Google's own password management services now. I expect that any "fix" from KunziSoft will be temporary in nature, and eventually, fall afoul of Google's Terms of Service.

ChromeOS won't even allow KeePass Android to launch at this time.

--Earl

On Mon, Dec 11, 2023 at 12:56 AM zunixnuz @.***> wrote:

Same here... KeePassDX 4.0.5 and latest ChromeOS. EACCES on writing the database on Google Drive. Keepass2Android can handle this situation without problems. Would be great to get a fix for this.

— Reply to this email directly, view it on GitHub https://github.com/Kunzisoft/KeePassDX/issues/808#issuecomment-1849500684, or unsubscribe https://github.com/notifications/unsubscribe-auth/APRODDX7JF7NA5GP36YEWE3YI24DVAVCNFSM4UTMQC3KU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBUHE2TAMBWHA2A . You are receiving this because you are subscribed to this thread.Message ID: @.***>

--

R. Earl (he/him/his),

Cybersecurity Central Grader

Boot Camp Spot

Email: @.***

[zunixnuz]

I suspect that Google is displeased with folks transferring a binary encrypted blob around,and also KeePass is a competitor for Google's own password management services now. I expect that any "fix" from KunziSoft will be temporary in nature, and eventually, fall afoul of Google's Terms of Service. ChromeOS won't even allow KeePass Android to launch at this time.

I dont't agree. KeePassDX is working with GoogleDrive on Android without problems. Also Keepass2Android is working with GoogleDrive on ChromeOS and Android without problems. Google does not block any blobs, that would make absolutely no sense.

[pmarks-net]

open failed: EACCES (Permission denied)

This smells similar to the bug I ran into with Keepass2Android Offline:

https://github.com/PhilippC/keepass2android/issues/1960#issuecomment-1251366262

If my theory is correct, the problem is that when you pick a file for reading, the handle can't later be used for writing, so you need to re-pick the same file for writing, overwrite the contents, and remember the new handle.

But KeePassDX lacks the "Tap OK to select a location... Overwrite?" feature. "Save a copy to ..." lets you save changes to a new file, but that's not enough.