Fedora 43 KDE, 2026.1.0.8 Flatpak, SQLite master key, "Always ask for password" option not respected

Fedora 43 KDE, 2026.1.0.8 Flatpak, SQLite master key, "Always ask for password" option not respected

avatar

Greetings,

Problem: RDM is not respecting "Always ask for password" option during SQLite data source creation.

Reproduction steps:

  1. Create a new SQLite source.
  2. Set a master key to this data source.
  3. Enable "Always ask for password".
  4. Prior to opening the first time, you will be greeted with the expected master password prompt.
  5. Enter password, data source opens.
  6. Close RDM.
  7. Reopen RDM.
  8. Observe that RDM did not ask you for a master password this time (or subsequent times).
  9. Observe that a .shk file was created on your disk in the ~/.rdm folder, that contains a cached (encrypted) version of the master key that enables automatic master key decryption upon opening RDM.


If RDM is told to not remember the password, then it should not cache it to disk.

All Comments (3)

avatar

Hello,

Thank you for the detailed report and reproduction steps.

I attempted to reproduce the behavior on my side using RDM with a SQLite data source and a master key, but I was not able to reproduce the issue. In my tests, the master password prompt appeared as expected when reopening the data source.

Could you please review the short video below and confirm whether your configuration matches what I tested? If there are any differences in your setup or the steps you follow, that might help us identify what is causing the behavior on your side.

Thank you.

Carl Marien

recreateion-of-the-issue.mp4

avatar

Carl,

Thank you for the video. For the record, what is shown in your video is exactly what I was doing. I am not able to reproduce this issue anymore (I have rebooted but that shouldn't matter here). I tried for like 30 minutes, and nothing. I had this long response typed out with further clarifications on my exact steps to reproduce.... but I ended up deleting them because I was unable to reproduce the issue.

Thanks for the help again.

avatar

Hello,

Thank you for the update. I appreciate you taking the time to test it again.

I'm glad to hear that the issue is no longer occurring on your side. If the behaviour does reappear at any point, please don't hesitate to let us know, and we will be happy to investigate further.

Thank you again for the follow-up.

Best regards,

Carl Marien