You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've read the option to encrypt the settings using YubiKey and such; however, I wonder:
"What is stopping you" from storing/probing the settings using the database itself?
I guess the socket-key needs to be stored outside; but what about the rest?
Ofc, maybe we should ask the KeePassXC team if they'd have any say on this (storing the settings, allowing one to piecewise give access to the DB), if you haven't had that studied extensively already
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've read the option to encrypt the settings using YubiKey and such; however, I wonder:
"What is stopping you" from storing/probing the settings using the database itself?
I guess the socket-key needs to be stored outside; but what about the rest?
Ofc, maybe we should ask the KeePassXC team if they'd have any say on this (storing the settings, allowing one to piecewise give access to the DB), if you haven't had that studied extensively already
Beta Was this translation helpful? Give feedback.
All reactions