Gilles Pion

Same problem happening to me. And, according to tcpview, TCP port 6000 is closed Have you found an explanation ?

Same problem happening to me. According to tcpview Port 6000 is closed Have you found an explanation ?

There is no "save all database" that I can see. Where is it in your KeePass? It's just here (I forgot the plural in the text of my post, but it is in the title) : Save will always (request to) perform a sync if the underlying database file has been modified since opening. You can force a sync without asking in Options > Advanced. I know that, but my question is related to the button next to it

There is no "save all database" that I can see. Where is it in your KeePass? It's just here : (I forgot the plural in the text of my post, but it is in the title) Save will always (request to) perform a sync if the underlying database file has been modified since opening. You can force a sync without asking in Options > Advanced. I know that, but my question is related to the button next to it

There is no "save all database" that I can see. Where is it in your KeePass? It's just here : Save will always (request to) perform a sync if the underlying database file has been modified since opening. You can force a sync without asking in Options > Advanced. I know that, but my question is related to the button next to it

There is no "save all database" that I can see. Where is it in your KeePass? It's just here : Save will always (request to) perform a sync if the underlying database file has been modified since opening. You can force a sync without asking in Options > Advanced. I know that, but my question is related to the button next to it

Hello, the "save database" button performs a sync even if the database is not marked as modified. Is there a way to have the "save all database" work identically ?

The security issue is whether the triggers can be modified by a malicious actor I fully understand the advantage in terms of enforced security of storing the triggers in the enforced configuration. It's only the fact that, when applying your suggested method ("add all triggers to the enforced config"), the consequence is that all triggers become de facto viewable by all user accounts of the machine, and I find that not very practical and I'm not comfortable with. Nothing more and not security related....