Mercurial > vim
diff runtime/doc/editing.txt @ 2581:e8a482a7fa6c
Updated runtime files.
author | Bram Moolenaar <bram@vim.org> |
---|---|
date | Sun, 19 Sep 2010 19:01:21 +0200 |
parents | 073ff46fe397 |
children | 916c90b37ea9 |
line wrap: on
line diff
--- a/runtime/doc/editing.txt +++ b/runtime/doc/editing.txt @@ -1,4 +1,4 @@ -*editing.txt* For Vim version 7.3. Last change: 2010 Jul 28 +*editing.txt* For Vim version 7.3. Last change: 2010 Sep 18 VIM REFERENCE MANUAL by Bram Moolenaar @@ -1431,13 +1431,15 @@ Notes: history, showing the 'key' value in a viminfo file. - There is never 100% safety. The encryption in Vim has not been tested for robustness. -- The algorithm used is breakable. A 4 character key in about one hour, a 6 - character key in one day (on a Pentium 133 PC). This requires that you know - some text that must appear in the file. An expert can break it for any key. - When the text has been decrypted, this also means that the key can be - revealed, and other files encrypted with the same key can be decrypted. -- Pkzip uses the same encryption, and US Govt has no objection to its export. - Pkzip's public file APPNOTE.TXT describes this algorithm in detail. +- The algorithm used for 'cryptmethod' "zip" is breakable. A 4 character key + in about one hour, a 6 character key in one day (on a Pentium 133 PC). This + requires that you know some text that must appear in the file. An expert + can break it for any key. When the text has been decrypted, this also means + that the key can be revealed, and other files encrypted with the same key + can be decrypted. +- Pkzip uses the same encryption as 'cryptmethod' "zip", and US Govt has no + objection to its export. Pkzip's public file APPNOTE.TXT describes this + algorithm in detail. - Vim originates from the Netherlands. That is where the sources come from. Thus the encryption code is not exported from the USA.