Jonathan White

Added another fix for the passphrase generator wordlist size handling:  I also added disabling the copy button on the TOTP dialog if the code is invalid

The buttons are only testing if totp is configured... that would be a bigger change to the code logic deep in the totp settings. I will consider this.

Ok well this turned out much easier than I expected and actually improves a lot of behaviors:   Give this a thorough test, but I think I hit everything,...

Good catch, probably just need to explicitly do an "enable" operation on the button since it used to be dynamic. and fixed it

What hasn't been fixed? I could not replicate your gif

Ah, I figured it out, fix inbound

There is a discussion here: https://github.com/keepassxreboot/keepassxc/issues/7571

This is a good proposal

@michaelk83 you are confusing two ideas. It is true that Secret Service API does not have any built-in protections between requestor and supplier. As you stated, any app can request...

You are still confusing the two roles based on my read of your post. The app requesting secrets _IS NOT IN CONTROL_ of those secrets. KeePassXC (ie, the end user)...