passkey can be saved even if database is readonly

[cryptosteve2]

Description I don't know if this is intentional, but a new passkey can be saved even when the database is open in read-only mode.

How to reproduce Steps to reproduce the behavior:

1. Set database readonly
2. try to add a new passkey
3. passkey will be saved

Expected behavior If the database is readonly nothing should be saved there. Or do I miss something?

Environment:

• Device: Mac mini M4 pro
• OS: MacOS Tahoe 26.0.1
• App Version: 2.4 (170) - btw: WELL DONE :)

[keepassium]

Saving (well, more like "caching with intention to be saved") is designed to work when AutoFill opens the last-seen local database due to some trouble (access timeout, original file not found, etc). These databases are non-editable in the main app (to avoid sync conflicts), but AutoFill would accept passkeys / new entries to be stored there — in case the access problem is transient and will later be solved.

However, saving is not supposed to work when "Read-only" is manually set in database settings.

• Is this in Safari?
• Do you get any KeePassium AutoFill UI during the process? Or only system dialogs?

[cryptosteve2]

My database is manually locked via database settings. And yes, it's in Safari. I think it's an system dialog, is it?

But it's ok when AutoFill is able to cache that passkey. The database itself in die app is locked as expected.

[keepassium]

@cryptosteve2, on a related note: when you open the database in the app itself — does it show "This database is read only"? If yes, does it show this in _all_the groups or only in the root?

(It seems something is off with the read-only enforcement, not only in AutoFill…)