I want to protect my passwords for free and store them on a machine that might get stolen but have the passwords very securely backed-up in the cloud, again for free, and minimize the total lifetime inconvenience of password management system changes and minimize the risk of transcription errors that might result from porting.
Some systems deviate from the usual 2-tuple access allowed by a user name and password. For example, for some systems I would store a 3-tuple because an email address may be allowed as an alternate user name. Others have a 4-tuple to allow for a password hint and secondary password. The diversity of systems has me preferring that the password file be free-format text.
My solution has been to cut-and-paste my free-format text file into CryptoTE and then encrypt the file using my ubuntu user password and upload the encrypted file to Google Drive (manually). My criteria are satisfied because
- CryptoTE is free for personal use
- Google Drive is free and uploads via SSL
- Google Account has a 2 step authentication that allows a level of security that I feel is very secure and yet still has convenient recovery protection
- Google is too large for it's business plan with respect to Drive to be often disrupted in a lifetime. It is certainly going to be larger than any pure-play password protection company for a long time.
- CryptoTE has a free-format text GUI that is devoid of formatting that might cause the contents to be hard to port
- I can migrate from a free-format linux text file to CryptoTE via a cut-and-paste
- I can migrate from CryptoTE via a cut-and-paste if that is ever going to be necessary because of the introduction of features that I might forget to eschew
- in the event I might someday use Windows on a daily basis, I can migrate using 'todos', or migrate back using 'frodos', and be comfortable because both line delimiting standards are decades old and likely to persist. (This step is probably unnecessary if CryptoTE for Windows exists, but why be married to CryptoTE if you don't have to be.)
- unlike some encrypting text editors CryptoTE does not leave un-encrypted temp files somewhere on the drive
Other than 1 - using a file password that is not the same as my ubuntu password, and 2 - obtaining and maintaining (or freezing) my own source code that does what CryptoTE does, and 3 - remembering to upload, what should I do to make this more secure or better in any aspect, while still meeting my criteria?
Issue 1 is not a big deal because I can just use a good password for my CryptoTE file.
Issue 3 is not a big deal because the probability of a computer being stolen is low. If a computer is stolen the worst case is that a cloud backup is one or two versions old if I forgot to upload the latest.
Issue 2 is the only one that worries me, however this is not a prohibitive issue. It will not be a worry at all with a little one time effort.
I note that Google Drive has an ugly user interface that might have the user accidentally sharing files but the interface might get better with time, and in the meanwhile, at least it is CryptoTE protected.