2 ms·
If they're gonna work around your "no password via argv" security design, it might be a reasonable thing to jst let them. Anyone who goes: hide add -n account
by bigiain 6y ago
If they're gonna work around your "no password via argv" security design, it might be a reasonable thing to jst let them. Anyone who goes:
hide add -n account -u user -p password123
And gets an error message saying "Sorry, you can't put the password into the command,it's a security problem in things like bash_history. Please use STDIN"
Then goes "Fuckit!":
echo 'password123' > hide add -n account -u user -p
Maybe they should be allowed to do that?
(I can almost imagine scenarios where someone might want to use a tool like this in some server automation thing where the security tradesoffs really do make using it like that a not awful idea?)