0.25.4
29th July, 2025
Fixed
- The PBKDF2Salt is no longer corrupted when attempting replication while the device is offline. (#686)
- If this issue has already occurred, please use
Maintenance->Rebuilding Operations (Remote Only)->Overwrite RemoteandSendto resolve it. - Please perform this operation on the most reliable device.
- On all other devices, we can perform
unlockon the warning dialogue during the first synchronisation after overwriting. It does not require a lot of traffic. - I am so sorry for the inconvenience; there are no patching workarounds. The rebuilding operation is the only solution.
- This issue only affects the encryption of the remote database and does not impact the local databases on any devices.
- (Preventing synchronisation is by design and expected behaviour, even if it is sometimes inconvenient. This is also why we should avoid using workarounds; it is, admittedly, an excuse).
- Very rarely, we can unlock the remote from the warning dialogue on receiving devices. We are performing replication, instead of simple synchronisation at the expense of a little complexity (I would love to express thank you again for your every effort to manage and maintain the settings! Your all understanding saves our notes).
- This process may require considerable time and bandwidth (as usual), so please wait patiently and ensure a stable network connection.
- If this issue has already occurred, please use
Side note
The PBKDF2Salt will be referred to as the Security Seed, and it is used to derive the encryption key for replication. Therefore, it should be stored on the server prior to synchronisation. We apologise for the lack of explanation in previous updates!