public/obsidian-livesync
1
0
Fork 0
mirror of https://github.com/vrtmrz/obsidian-livesync.git synced 2026-10-17 14:52:32 +00:00
Code Issues Packages Projects Releases Wiki Activity

Preserve configuration encryption edits when applying settings

Browse Source
This commit is contained in:
vorotamoroz
2026-10-13 04:18:57 +00:00
parent 14141446a1
commit db9f7af4f1
11 changed files with 720 additions and 71 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/settings.md
+5 -1
View File
@@ -988,10 +988,14 @@ If this option is enabled, PouchDB will hold the connection open for 60 seconds,
Setting key: configPassphraseStore
Choose how the passphrase for sensitive configuration items is provided. **Default** uses the existing default key. **Use a custom passphrase** uses the value of `configPassphrase` and saves that key on this device. **Ask an passphrase at every launch** requests a masked passphrase at start-up and caches a successfully entered key in memory for that launch.
Apply this setting and its passphrase together. Applying them re-encrypts the saved sensitive values with the selected passphrase and changes how LiveSync obtains that passphrase in one operation. If Apply fails, the edited values stay available for another attempt. Re-encryption preserves the plaintext values: it does not change the E2EE passphrase, the ID key, or Vault contents.
#### Passphrase of sensitive configuration items
Setting key: configPassphrase
This passphrase will not be copied to another device. It will be set to `Default` until you configure it again.
This passphrase is not copied to another device. With **Use a custom passphrase**, the selected mode is stored in the configuration but the key remains on this device. If protected settings need to be decrypted and another device does not have the key, LiveSync asks for the passphrase during start-up. After the protected settings validate it, the key is saved on that device.
### 4. Developer