Itu tidak aman. David Leadbeater memposting kode POC ke brute-force hingga 64 byte dalam sebuah artikel berjudul, agak ironisnya, enkripsi blowfish Vim ... atau mengapa Anda tidak harus menggulung crypto Anda sendiri . Dokumentasi Vim sekarang merekomendasikan :
- The implementation of 'cryptmethod' "blowfish" has a flaw. It is possible
to crack the first 64 bytes of a file and in some circumstances more of the
file. Use of it is not recommended, but it's still the strongest method
supported by Vim 7.3 and 7.4. The "zip" method is even weaker.
Dan, sebelumnya:
The text in the swap file and the undo file is also encrypted. E843
However, this is done block-by-block and may reduce the time needed to crack a
password. You can disable the swap file, but then a crash will cause you to
lose your work. The undo file can be disabled without much disadvantage.
:set noundofile
:noswapfile edit secrets
Note: The text in memory is not encrypted. A system administrator may be able
to see your text while you are editing it. When filtering text with
":!filter" or using ":w !command" the text is also not encrypted, this may
reveal it to others. The 'viminfo' file is not encrypted.
Ringkasan:
- Jika Anda peduli dengan keamanan,
blowfishsebaiknya tidak digunakan. Gunakan blowfish2sebagai gantinya.
- Sementara
swapdan undofile dienkripsi, viminfotidak.
Saran yang tidak diminta:
- Jika Anda peduli dengan keamanan, jangan gulung enkripsi Anda sendiri . Dan itu berarti
blowfish2implementasinya juga. Gunakan sesuatu yang lain, seperti GPG. The gnupg.vimPlugin mungkin berguna. Sepertinya tetap dipertahankan . Ini menonaktifkan viminfodan file swap.