Benjamin Fritz wrote: > > On Wed, Mar 23, 2016 at 4:58 PM, Bram Moolenaar <[email protected] > <mailto:[email protected]>> wrote: > > > > > Speaking of defaults: I think Vim should default to the strongest > > > method available. I additionally think Vim should warn on saving with > > > a known broken format such as the original blowfish implementation, or > > > the zip algorithm, or even blowfish2 without a decent KDF. Maybe even > > > compile without the broken algorithms altogether unless the user > > > specifically passes --include-bad-crypto to the configure script or > > > something. > > > > This has the danger of writing a file on one system, go on holiday and > > find out you can't open it on your laptop (that actually happened to > me). > > > > That makes some sense, however it only applies to people who edit the > same file on multiple systems, AND they don't have the same version of > Vim on each of those systems. And, if libraries are used, the system may update the library (while one is on holiday), potentially rendering encrypted text unreadable. I know that these things should be done in a backwards compatible fashion, but Murphy's Law plus having many users guarantees trouble will happen.
I agree that libraries will get better testing, though. Chip Campbell -- -- 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]. For more options, visit https://groups.google.com/d/optout.
