Quite frequently, I need to take a quick textual note but when the content is sensitive, even just transiently, well, some things shouldn’t be left around on disk in plain text. Now before you pipe up with “but I encrypt my home directory” keep in mind that that only pretects data against it being read in the event your machine is stolen; if something gets onto your system while it’s powered up and you’re logged in, the file is there to read.
So for a while my workflow there has been the following rather tedious sequence:
$ vi document.txt $ gpg --encrypt --armour -r email@example.com -o document.asc document.txt $ rm document.txt $
and later on, to view or edit the file,
$ gpg --decrypt -o document.txt document.asc $ view document.txt $ rm document.txt
(yes yes, I could use default behaviour for a few things there, but GPG has a bad habit of doing things that you’re not expecting; applying the principle of least surprise seems a reasonable defensive measure, but fine, ok
$ gpg < document.asc
indeed works. Pedants, the lot of you).
Obviously this is tedious, and worse, error prone; don’t be overwriting the wrong file, now. Far more serious, you have the plain text file sitting around while you’re working on it, which from an operational security standpoint is completely unacceptable.
I began to wonder if there was better way of doing this, and sure enough, via the volumous Vim website I eventually found my way to this delightful gem: https://github.com/jamessan/vim-gnupg by James McCoy.
Since it might not be obvious, to install it you can do the following: grab a copy of the code,
$ cd ~/src/ $ mkdir vim-gnupg $ cd vim-gnupg/ $ git clone git://github.com/jamessan/vim-gnupg.git github $ cd github/ $ cd plugin/ $ ls
Where you will see one
gnupg.vim. To make Vim use it, you need to put in somewhere
vim will see it, so symlink it into your home directory:
$ mkdir ~/.vim $ mkdir ~/.vim/plugin $ cd ~/.vim/plugin/ $ ln -s ~/src/vim-gnupg/github/plugin/gnupg.vim . $
Of course have a look at what’s in that file; this is crypto and it’s important to have confidence that the implementation is sane. Turns out that the
gnupg.vim plugin is “just” Vim configuration commands, though there are some pretty amazing contortions. People give Emacs a bad rap for complexity, but whoa.
:). The fact you can do all that in Vim is, er, staggering.
Anyway, after all that, it Just Works™. I give my filename a
.asc suffix, and ta-da:
$ vi document.asc
the plugin decrypts, lets me edit clear text in memory, and then re-encrypts before writing back to disk. Nice! For a new file, it prompts for the target address (which is one’s own email for personal use) and then on it’s way. [If you’re instead using symmetrical encryption, I see no way around creating an empty file with
gpg first, but other than that, it works as you’d expect]. Doing all of this on a GNOME 3 system, you already have a
gpg-agent running, so you get all the sexy entry dialogs and proper passphrase caching.
I’m hoping a few people in-the-know will have a look at this and vet that this plugin doing the right thing, but all in all this seems a rather promising solution for quickly editing encrypted files.
Now if we can just convince Gedit to do the same.