I have a keepassxc database with passwords on my laptop with Lubuntu. I have a backup on flash drive via rsync. I'd like to use the same database on my Android phone and Windows machine at work as well. What is the most efficient and secure way to have a database synchronized (actual) and utilize it on all of these devices? Now, I have an idea of a cumbersome solution. To bring the flash with synchronized database every day to my work and have another copy on Android phone. What is a better solution?

I wanted to know whether KeePassXC and KeePass are compatible with Solaris (I am using Solaris 11.4.26.75.4 (sun4v / sparc architecture)). I would need to use only the KeePassXC/KeePass command line interfaces, the KeePassXC/KeePass GUIs are not necessary. I do not have admin rights / sudo access, so I cannot install the software myself, but I may ask the responsible unix support team (which has admin access) to attempt the installation. However, before doing that, I wanted to ask regarding the Solaris compatibility here in the forum. Under the respective download pages, Solaris is not listed among the supported OS. **KeePassXC:** can be built from source , but again Solaris is not included as a supported OS on the Building KeePassXC wiki page (see Required Dependencies) . **KeePass:** Googling yields a few links that might indicate Solaris compatibility (Forbes article 1 (July 2023) , Forbes article (March 2023) , KeePassX forum link ), but I am not 100% certain. **Question: Can KeePassXC (preferred if possible) and/or KeePass be successfully built/installed from source and used on Solaris? Do you maybe know any tests/links explicitly giving this information?**

I would like to be able to secure a KDBX _key file_ in my $HOME, so that nobody except keepassxc (and root) can access it, __excluding even myself__. My only approach is to use the setgid bit on the executable/s and give the key file corresponding group membership but unfortunately, keepassxc's GUI is a GTK+ application, that does not like setuid or setgid bits and terminates itself, when detected. To setup a test environment with a dummy KDBX vault and a key file:

sudo addgroup keepassxc

sudo chgrp keepassxc $(which -P keepassxc)
sudo chmod g+s $(which -P keepassxc)

# to revert back afterwards:
# sudo delgroup keepassxc
# sudo chgrp root $(which -P keepassxc)
# sudo chmod g-s $(which -P keepassxc)

# create test files
keepassxc-cli db-create -p -k key.file test.kdbx
chmod -rwx,g+r key.file
sudo chown root:keepassxc key.file

# access test
keepassxc --keyfile key.file test.kdbx # should succeed
sha256sum key.file                     # should fail

but, like i said, the keepassxc GUI terminates with

Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.

(process:102257): Gtk-WARNING **: 19:45:45.157: This process is currently running setuid or setgid.
This is not a supported use of GTK+. You must create a helper
program instead. For further details, see:

    http://www.gtk.org/setuid.html 

Refusing to initialize GTK+.

I refuse to fiddle around with keepassxc any further. There are good reasons for the restriction of setu/gid bits for sure. Do you know a solution for my approach? Is it even preferable? Is there an easy template/solution for mentioned helper program? Bash only? Are there better ways to achive my goal of limited file access to a single executable?

I do have an issue passing on password to keepassxc-cli in bash. I would like it to unlock and ask for adding a password on KeePassXC entry. When I ask user for a password e.g. read for KeePassXC DB password and I use it to unlock it multiple times: **This works:** echo $passwordForKeepassDatabase | keepassxc-cli add "$keepassxcDatabase" "$databaseGroup/$databaseEntry $currentYear" However, when I need to unlock the KeePassXC DB and simultaneously ask the user for the entry password it does not work. The KeePassXC DB password is used in both cases. **The following does not work correctly** (as it uses the DB password for both prompt - notice the added -p switch): echo $passwordForKeepassDatabase | keepassxc-cli -p add "$keepassxcDatabase" "$databaseGroup/$databaseEntry $currentYear" Any idea for a workaround? I would like to re-use the already entered KeePassXC DB password and then ask the user to enter a password for the new KeePassXC entry.

Today I had to restart my computer after a total freeze of Linux. After that I now have the problem that **KeepassXC 2.7.1 leads to a immediate logout of my Linux system as soon as I try to use the auto-type functionality**. It doesn't matter if it should type a user name, a password or both. I also tried different credentials - the problem stays the same.
In the weeks before I never had this problem, using this function very often.
=> __What could be the root cause for that problem?__

- Another odd thing is that KeePass asks now for a confirmation if it should auto-type into the window which was active before. It never posed this question before. I know this is a setting but I never changed this setting. - A second restart of Linux didn't solve this problem. After the restart I get the information that there is no space on partition /boot. But there are 82MB free space on this partition.

I use keepassxc (my password manager) to manage my ssh keys. This means the keys are stored within the database (not stored on disk in a traditional way). When I unlock my password database, all keys are added to the agent. However, with a growing list of ssh keys, I get the problem that ssh tries all the keys in the agent, which results in Too many authentication failures if the remote host allows less authentication tries than i have ssh keys (and the particulary ssh key is far back in the list). Is there a way to tell ssh: "for this host, use the key with fingerprint xyz, fetch it from the agent"? Alternatively pubkey xyz, but I can't use the IdentityFile option (and IdentitiesOnly yes), since I don't want to store my private keys on disk.

How to change decrypt time of KeePassXC database after beng created?

**Background:** KeePassXC 2.6.6 is the latest version from June. My computer is newer than that, so this is the only version I've ever run on it, installed from deb http://ppa.launchpad.net/phoerious/keepassxc/ubuntu focal main from the start. I'm running Linux Mint 20.3 (with MATE 1.26.0). Everything was working fine until a few days ago. **Problem:** For some reason, KeePassXC is now always modal: - Alt-tabbing to another program (or clicking another program's taskbar button) gives the other program the focus (even the keyboard) but leaves KeePassXC on top. I.e., I'm typing underneath the window I'm looking at. - Even hitting the start button to bring up the Mint menu causes it to come up underneath KeePassXC. - This is all true whether KeePassXC is fullscreen or not, and it doesn't matter if I'm in an entry, at the main list, or looking at search results. **Workaround (not great---impedes normal workflow quite a bit):** Now the only way to get KeePassXC from covering other programs is to minimize it. **Answers I *think* I've ruled out:** - Since KeePassXC itself wasn't updated, I'm not sure it's the source of the problem, even though it's the only program exhibiting this behavior. - One of its dependencies is Qt 5, but that (well, a bunch of libqt5* packages, but none of the other ones listed like qtbase5), according to dpkg.log, was last updated Jan 7th, quite a bit longer ago than when I believe the problem started happening (~Jan 20th). - None of the other dependencies have been updated since Jan 7th. - I haven't touched any of the settings within KeePassXC. - Full cold boots do not fix the problem. **Question:** What other system updates or changes could have broken it?