Timeline for How to prevent sensitive CLI arguments being logged in journalctl while using sudo?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 4, 2017 at 0:18 | history | edited | user180574 | CC BY-SA 3.0 | added 144 characters in body |
| Apr 4, 2017 at 0:16 | vote | accept | user180574 | ||
| Apr 3, 2017 at 6:37 | comment | added | Kenneth B. Jensen | To add onto what @thrig said, try using a text editor on an intermediate file (i.e. vim file.txt), type the password onto that, and invoke the command as sudo set_account.sh --password $(head -n1 file.txt) --pin-number $(head -n1 file2.txt) | |
| Mar 31, 2017 at 22:09 | history | edited | Gilles 'SO- stop being evil' | edited tags | |
| Mar 31, 2017 at 19:47 | history | tweeted | twitter.com/StackUnix/status/847898118360313856 | ||
| Mar 31, 2017 at 18:21 | answer | added | Neil McGuigan | timeline score: 1 | |
| Mar 31, 2017 at 18:06 | answer | added | Ned64 | timeline score: 0 | |
| Mar 31, 2017 at 17:22 | comment | added | thrig | Can set_account.sh instead read the password from the tty? Otherwise it will appear in the process list, which most anyone can view. | |
| Mar 31, 2017 at 17:11 | history | edited | user180574 | CC BY-SA 3.0 | deleted 2 characters in body |
| Mar 31, 2017 at 16:58 | review | First posts | |||
| Mar 31, 2017 at 17:02 | |||||
| Mar 31, 2017 at 16:55 | history | asked | user180574 | CC BY-SA 3.0 |