On Mo, 18 Mai 2020, 'Andy Wokula' via vim_dev wrote:
> Am 15.05.2020 um 22:31 schrieb Bram Moolenaar:
> > Patch 8.2.0762
> > Problem: Buffer is not considered modified after setting crypt key.
> > Solution: Set the modified flag. (Christian Brabandt, closes #6082)
> > Files: src/optionstr.c, src/testdir/test_crypt.vim
> >
> >
> > *** ../vim-8.2.0761/src/optionstr.c 2020-04-17 19:41:16.100078313 +0200
> > --- src/optionstr.c 2020-05-15 22:28:34.399878939 +0200
> > ***************
> > *** 1157,1164 ****
> > --- 1157,1167 ----
> >
> > if (STRCMP(curbuf->b_p_key, oldval) != 0)
> > // Need to update the swapfile.
> > + {
> > ml_set_crypt_key(curbuf, oldval,
> > *curbuf->b_p_cm == NUL ? p_cm : curbuf->b_p_cm);
> > + changed_internal();
> > + }
> > }
>
> Does it really do a before-after comparison of the key?
> If so ... maybe ... will this make it easier to guess a key?
> Ie, just guess a key and then check 'modified'?
>
> I would have expected that any :X command sets the modified flag.
It does a comparison and checks, if a new key has been entered and that
one differs from the previous active key. If not a new key has been
entered than the old key will be still in play. So it does not directly
relate to guessing the key value, it assumes the buffer has been
successfully decrypted before.
Best,
Christian
--
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/20200518114630.GA16708%40256bit.org.
