fix: a reload keeps the document protected, and the first save asks for the password
The password itself is never stored, so a reload left the document open and the next save wrote the protected file unencrypted without a word. The fact of the protection now survives; the save dialog asks for the password again or lets the protection go, and backing out cancels the save.
This commit is contained in:
1 parent
87743fdd57
commit
cb0db7dd96
7 files changed
+65
-7
No files matched your search
@@ -19,7 +19,10 @@ Encryption is the **last** thing to touch the bytes: `writeHandle`/`download` in
|
||||
.odt into an .ott. Decryption is the **first**: the top of `applyImport` in `App.svelte`,
|
||||
before `convertUnsupportedImages`, which would otherwise unzip an encrypted archive and find
|
||||
nothing. The password lives in `docPassword` for the session only — the autosaved copy in
|
||||
localStorage stays plain text, as both reference word processors' recovery copies do.
|
||||
localStorage stays plain text, as both reference word processors' recovery copies do. What
|
||||
survives a reload is the fact of the protection (`edentext-doc-protected`): the first save
|
||||
then asks for the password again, or for the protection to be lifted, so a reload never
|
||||
turns a protected file into an open one.
|
||||
|
||||
## ODF
|
||||
|
||||
|
||||
Reference in new issue
Block a user