Sign when writing files that were signed and verify signed files when opening #34
Comments
hlein
added a commit
to hlein/vim-gnupg
that referenced
this issue
Oct 12, 2019
When editing an existing file, check if the source file was signed, and if so, enable signing when we save it. When writing out a file, moved the "should we sign" check so that it always happens. When saving an existing file, b:GPGOptions exists already, so g:GPGPreferSign was not being checked previously. This partially addresses jamessan#34 If we wanted to support selecting between different private keys to sign with, then checking _which_ key had signed a file and looking for a corresponding private key in our keyring could be done in the --list-packets check. But that is another future issue & PR.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi James,
By reading the source I got the impression that when writing files are only signed if the variable
g:GPGPreferSignis set to 1, regardless of whether the file was signed to begin with. Assuming my interpretation of the code is right (I don't know any vimscript), I was wondering if the plugin should check if the encrypted file is signed while decrypting it andlet b:GPGOptions += ["sign"]accordingly.gpg --decrypttells you if the signature could be verified in the last 2 lines written to stderr:Using this same information signed files can be verified when opening them :)
Files that aren't signed just don't write those last 2 lines to stderr.
Cheers,
Ricardo
The text was updated successfully, but these errors were encountered: