On Tue, Feb 16, 2016 at 10:27 PM, Matthew Winn <[email protected]> wrote: > On 16/02/16 16:43, Aaron Toponce (Vim Github Repository) wrote: >> >> The goal with this issue, is to provide authenticated encryption to the >> ciphertext, so not only is data integrity maintained, but also prevents >> external modification without knowledge of the authentication key to produce >> a new MAC. So, not only do we get data privacy with Blowfish, but we get >> authentication with HMAC-SHA256. > > > Shouldn't that sort of task be delegated to an external application? Vim is > a text editor, not an evidential data integrity suite. > > -- > Matthew Winn
+1 I don't use Vim for crypto (though having it in doesn't bother me), I use it to edit plaintext (including XML-based application/x MIME types such as application/xhtml+xml, application/xul+xml, application/rdf+xml, etc.). If I want to send an encrypted message (and sometimes I do) I encrypt it outside of Vim by means of some application which the addressee (who doesn't always have Vim) is expected to have installed. AFAIK, Vim cryptography is not perfect (nothing is) but it isn't broken, so I keep hands off from trying to "fix" it. Best regards, Tony. -- -- 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.
