On Do, 17 Jun 2021, Gary Johnson wrote:
> 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.
What I was trying to say was, that I do not see other reasons for
keeping the blowfish code *except* for being able to read older
encrypted files (and maybe also for as long as it is marked
experimental). I was not trying to imply, that we should remove the
blowfish code.
We also still carry the old crypt-zip code around, even so I doubt
anybody is using that one. But at least I do not plan on removing it
(and I think it would be a mistake to do so for the reasons you have
mentioned).
Best,
Christian
--
Wo es den Rednern an Tiefe fehlt, da gehen sie in die Breite.
-- Charles-Louis de Montesquieu
--
--
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/20210618071239.GL532641%40256bit.org.
