3 ms·
This is why I've grown to consider some actions to taint terminal windows, and tainted windows must be destroyed asap. For example, administrative access to va
by tetha 9y ago
This is why I've grown to consider some actions to taint terminal windows, and tainted windows must be destroyed asap.
For example, administrative access to vault requires a root token in the environment of the shell, so that shell is tainted with too much access. Having an ssh-command to a productive data storage also taints a shell, because it's really dangerous to accidentally up-arrow-enter and then you end up on a productive data storage.
History has been a bit annoying with that, but since I installed histdb, that has been a non-issue.
- bogomipz 9y agoI'm not familiar with histdb. How does that resolve the issue of of tainted environment?
- tetha 9y agoI'm a heavy user of my shell history. Frequent creation and destruction of different concurrent shell sessions clobbers the history quite well until there's nothing really usable left. This resulted in some inertia to keep windows around. zsh-histdb replaces the single-file ~/.zsh_history with an sqlite3-database - and this database is session aware. This way I can just have as many concurrent session as I want, and create / destroy shell sessions as much as I want and the shell history remains intact.