Angelelz
Collect new entries from Slave DB
Hello! I have sync job of a group from master to slave. If I add a new entry in that group in slave database, after sync it's dissapears! Can I copy new entries from slave DB to master? Thanks
I use this plugin to securely share bank and family entries with my wife. What I do:
Master DB: -Everything I need to share with her I put in a group named "wife" Configuration Entry: -Title: wife -Password: Wife DB Pass -Custom Fields: --MSS_Group: wife --MSS_TargetFilePath: Path to wife DB
Slave DB: -Everything she wants to share with me she puts in a group named "share" Configuration Entry: -Title: share -Password: [Leave Blank] -Custom Fields: --MSS_Group: share --MSS_IsSlave: true --MSS_TargetFilePath: Path to my DB
That way, slave DB does not need to know the Master DB password.
Notice the entries I share are separated from the entries she shares (Different groups). If you want all the entries in the same group. you could add different tags to those entries created by the master, and a different tag to the entries created by the slave. Then, your configuration entry should have MSS_Group and MSS_Tag for the corresponding entries. Let me know if you need more clarification.
I just removed “MSS_PerformSlaveJobs” field from slave DB entry and all works now! Thank you very much, Bro! J
From: Angelelz [email protected] Sent: Saturday, October 19, 2019 7:08 PM To: Angelelz/KeePassMasterSlaveSync [email protected] Cc: Cobblestone-TLT [email protected]; Author [email protected] Subject: Re: [Angelelz/KeePassMasterSlaveSync] Collect new entries from Slave DB (#5)
Notice the entries I share are separated from the entries she shares (Different groups). If you want all the entries in the same group. you could add different tags to those entries created by the master, and a different tag to the entries created by the slave. Then, your configuration entry should have MSS_Group and MSS_Tag for the corresponding entries. Let me know if you need more clarification.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Angelelz/KeePassMasterSlaveSync/issues/5?email_source=notifications&email_token=ANRCKNKPXRAHCBOUXNMQRW3QPMPGPA5CNFSM4JCP54V2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBXS5BY#issuecomment-544157319 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ANRCKNMFAKS3SBP3X32PKTTQPMPGPANCNFSM4JCP54VQ .
I would like to bump this issue.
Even though the use case for bidirectional sync is covered by your mechanism, it requires that the slave crypt has the password to the master crypt.
I have a use case in which I would like to set up bidirectional sync WITHOUT recording the master crypt's key in the slave.
in the Master database, in the Sync entry, add. MSS_PerformSlaveJobs
In the slave db, in the Sync entry add. MSS_IsSlave
I have no idea why I still get the missing password notification while the sync both ways seems to be working: "MasterSlaveSync: Missing Password or valid KeyFilePath for: Sync app passwords to master"
Master database: \MSSyncJobs\Sync to mobile\
- Password = password of the Slave database
- MSS_PerformSlaveJobs = True
- MSS_TargetFilePath = path of the Slave database
- MSS_Group = all the necessary groups including the "App"
Slave database: \MSSyncJobs\Sync app passwords to Master\
- Password: not set
- MSS_IsSlave = True
- MSS_TargetFilePath = path of the Master database
- MSS_Group = App (this is the group which would be usually updated on the mobile when the Keepass2Android saves login details from an app)
