[drostie]

After I wrote my "nermal" project (npm-installable JS authenticated-encryption container) I wrote a password manager as an example, which I called "tagaloop". Some documentation for it is available here:

https://github.com/drostie/nermal/tree/master/examples

In particular, I avoided the command-line interface precisely because the other tool on that page, ncrypt, would tend to leak inline passwords and such to log files. For various reasons those options were necessary to perform the job it required (e.g. in a script which is chmod root 500, for example) but not required for its use (it will just prompt you for the info if you leave the flags off).

In particular, the -a "add" option in Steel will probably save passwords to ~/.bash_history, no?

[dyladan]

Not only that, but command line options are generally not secure from other users on the system. Just running `ps -ef` can read command line options from any user. A more secure alternative would be running the program in an interactive mode.