Getting started Opening an existing database What happens if my phone gets lost or stolen? Do I know how to recover my database from a backup or the cloud?.What happens if I have an accident? Should any trusted person be able to access my database?.This means that if you forget the master password, your database is lost! So make sure you remember the password and retain any second factor method (if one is used). knowing the master password (and additional second factor if you chose one).There is no way for anyone, including the app’s author, to access the information stored in your password database without.It is your responsibility to backup this file regularly and safely. Keepass2Android stores your password in an encrypted file.If you store important information using Keepass2Android, you should know a little bit about what’s going on: If you think something is missing in the documentation, please create an issue at What you should know and think about If you want, I’d be happy if you contribute texts for this place! More documentation will be added as requests come in or when the app is more feature stable. KeeShare works in principle really great, but is almost unusable because of the bug.Note: This is an incomplete and preliminary documentation. Would be happy if someone could take a look at this problem. The retrieval of the data and the transfer to the parent database must not result in a save. If a *.kdbx.share is only saved (and consequently stored with a new timestamp) when there is a real change of entries. The problem could probably be solved relatively easily: NOTE: # During synchronization the *.kdbx.share file is read and then stored with a new timestamp, which triggers a data synchronization for the linked instances. The file should not be stored again with new timestamp. NOTE: # For synchronization the *.kdbx.share file should probably be retrieved read-only. If one instance has crashed, it is possible to work normally again on the remaining instance. This leads to the fact that on PC2 by the change of the timestamp a call of the data takes place, which are stored again with new timestamp.īoth instances are in an endless loop, which can only be terminated manually or by the crash of the program. The *.kdbx.share is retrieved and now stored again with a new timestamp. The instance on PC1 now recognizes from the change of the timestamp field *.kdbx.share on the server that the file has been changed. If now KeePassXC is started on PC2, the same happens: the *.kdbx.share files are retrieved and for some reason saved again (see timestamp). As long as only one instance accesses the *.kdbx.share at the same time this is surely no problem. Steps to ReproduceĪ synchronization of the KeeShare files *.kdbx.share takes place.įor some reason, each single *.kdbx.share is then saved again. Then both instances get into a loop of retrieving the changes and saving until one of the programs crashes. However, there is a problem if KeePassXC with activated KeeShare is running on both PCs at the same time. The exchange of entries is in principle problem-free in both directions (import / export from PC1 to PC2 and vice versa). I have set up KeeShare for several folders and placed the *.kdbx.share files on the shared NAS. import/export) and stored personal certificates. To be able to share entries between the two databases, I recently enabled KeeShare (incl. The databases are stored on the shared NAS. I use KeePassXC on two PCs with different databases.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |