I haven't had to synchronize before - so all I ask is for those who do itĪll the time to confirm or deny that supposition. In summary, I think the Synchronize is NOT looking at the data inside theįile, but I think the Synchronize is ONLY looking at the date stamp of the Otherwise, Windows won't add the Android password when I synchronize! I have to FORCE the Android to have a newer date stampĭ. And then I add a password on the desktopĬ. I guess, once I know better how it works, the methodology is to ensure theĭATE STAMP of the kdbx file is always NEWER if I want to us Synchronize.ī. If the actual DATA on Androlid is newer than the data on Windowsī. The algorithm Keepass _should_ use, IMHO, is to LOOK at the data.Ī. If that's true - that's an utterly stupid algorithm! (IMHO). Then Windows IGNORES ALL DATA in the synchronization command If the Windows kdbx has a later datestamp than the Android kdbxī. I think Keepass on Windows simply looked at the DATE STAMP!Ī. I think I figured out why - but if that's why - it's really stupid. When I tried to synchronize, it didn't take anything from Import that "master" desktop passwd file into the phone.īut recently, I added a passwd on the phone, and then had to get that back Edit the "master" passwd file on the desktopī. Up until now, I've been using "IMPORT" where the general use model was:Ī. Mainly (but not always), I edit on the desktop (using a keyboard),īut _sometimes_ I find myself, on the road, adding a password on the phone. Where passwords are good since Keepass works on all platforms. I'm still formalizing my strategy for keeping my personal data off the net, Import (this seems to replace the entire file, I think) Synchronization (this does not work the way I thought it worked)Ģ. It seems there are two completely different things on Android.ġ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |