![]() "master" kdbx, which I can do with a simple "touch" command process on the The main caveat to that synchronize step is that I have to ensure that theĭATE STAMP on the mobile kdbx is at a LATER date than the date stamp of the On the desktop, SYNCHRONIZE the "mobile" kdbx with the "master" kdbx Once in a while, add/change passwds on the "mobile" kdbxĬ. Continue to add/change passwds on the "master" desktop kdbxī. Once in a while, this will be my SECONDARY use model, moving forward:Ī. ![]() On Android - IMPORT that "master" desktop kdbx Add/change password on the "master" desktop kdbxī. Given that oddity, I think this will be my MAIN use model, moving forward:Ī. What's interesting is that there does NOT seem to be a SYNCHRONIZE command O KeePass Password Safe, Windows 10, version 2.39.1) While there is a SYNCHRONIZE command on the Windows KeePass: The SYNCHRONIZE command does not seem to even _exist_ on the Android app! > file, but I think the Synchronize is ONLY looking at the date stamp of the > In summary, I think the Synchronize is NOT looking at the data inside the Less than I do - which - well - that's surprising if that's true. NOTE: It's odd that I'm the one pushing the technology since I'm not at allĭoing anything complicated - but I guess that means most people do even 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)Ģ. Syncthing is awesome, and I would love it if this could be fixed.It seems there are two completely different things on Android.ġ. My file systems are ext4 everywhere and I haven’t done any special stuff like running a custom kernel. ![]() My laptop runs 14.04 LTS and my desktop 15.04, both 圆4. I don’t wanna lose work.īoth my systems run Ubuntu. I still want sync-conflict files when an actual concurrent modification occurred. How do I get Syncthing to put its sync-conflict files in some other directory (like Btsync did/does), so that they do not interfere with special programs reading the files.How do I stop Syncthing from making sync-conflict files when there’s obviously no conflict?.I came from Btsync and it didn’t have these issues (it had other issues, however). I share some git projects between my devices with Syncthing and I have seen it create entire new branches with “sync-conflict” in the name, but this is by far the worst I have seen. Syncthing litters all my shared directories with “sync-conflict” files. This is not the first time I’ve seen this. 6! Whilst my desktop didn’t make any modifications to the file! It even made a sync-conflict for another sync-conflict. I did not touch the backup file on my desktop as it was being synced, however Syncthing managed to create 6 sync-conflict files. This was on my laptop, whilst my desktop was powered with Syncthing running. So, today I made a backup of an SD card with dd (the Unix utility).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |