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 am trying to use the KeePassHttp plugin with multiple computers that all sync the keepass database though dropbox. Whenever I go to open it on another computer it no longer works because KeePassHttp has no way of setting a different key for each computer. It always overwrites the previous association when a new one, hence their is no way to associate multiple PCs.
The text was updated successfully, but these errors were encountered:
Specify a new name when requesting an association.
I typically name my assocations "BrowserName (ComputerName)"
If you use the same name, then you'll overwrite any previous association.
This is used in conjunction with the notification bubble to let you know exactly what is using your password info and when.
----- Original Message -----
From: "Derek Chafin" reply@reply.github.com
To: "Perry" pfnguyen@hanhuy.com
Sent: Monday, November 28, 2011 3:13:12 PM
Subject: [keepasshttp] Don't overwrite the previous association for requests on other computers or browsers (#35)
I trying to use the KeePassHttp plugin with multiple computers that all sync the keepass database though dropbox. Whenever I go to open it on another computer it no longer works because KeePassHttp has no way of setting a different key for each computers. It always overwrites the previous association when a new one, hence their is no way to associate multiple PCs.
Reply to this email directly or view it on GitHub: #35
I am trying to use the KeePassHttp plugin with multiple computers that all sync the keepass database though dropbox. Whenever I go to open it on another computer it no longer works because KeePassHttp has no way of setting a different key for each computer. It always overwrites the previous association when a new one, hence their is no way to associate multiple PCs.
The text was updated successfully, but these errors were encountered: