On 2021-06-17, Christian Brabandt wrote: > On Do, 17 Jun 2021, Bram Moolenaar wrote: > > > > Yes, blowfish is kept separate. But the `XChaCha20-Poly1305` uses the > > > `crypt_pwhash` API and it also uses the `randombytes` API for the salt > > > and the seed. > > > > > > I did not want to touch the blowfish code for now, as I don't know, if > > > this is backwards compatible (e.g. if this will can still decrypt > > > existing blowfish encrypted files (swap files, undofile, files)) > > > > If libsodium is available, would there be any reason to use blowfish, > > other than reading existing encrypted files? Probably not, thus > > changing the blowfish crypt is not helping. > > No I don't think so
I may not understand what you're saying, but you aren't thinking of disabling the use of blowfish2 for updating existing encrypted files, are you? That would make it very difficult if not impossible to use various versions of Vim to view and update encrypted files. There are various needs for encryption. I don't need to hide anything from foreign agent crypto experts. I just want to keep some information hidden from other people who might use my computers. A reasonably secure code will do just fine, but having to keep track of which Vim can access which encrypted files is not OK. Regards, Gary -- -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/20210618014250.GA30040%40phoenix.
