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
--
--
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.
