| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 2 years, 1 month |
| seen | Apr 29 at 18:42 | |
| stats | profile views | 21 |
|
May 7 |
comment |
Can I have my shell history record how wildcards expanded? @Caleb: I'm assuming such a shell would only be part of a larger system where what the user can do is fairly controlled by other means already. I didn't mean to imply a custom shell by itself would accomplish anything security wise ;p |
|
May 5 |
comment |
Can I have my shell history record how wildcards expanded? @Giles: When I said make a shell I meant create a whole new one from scratch, where you'd have to build in limitations to prevent that sort of thing. You're definitely right that writing a fool proof config is probably impossible. |
|
May 1 |
comment |
Can I have my shell history record how wildcards expanded? If nobody adds another answer in a few days I'll mark as accepted, I think you're right. It would be interesting to try to make a shell where the history was more suitable for assisting with audits. |
|
May 1 |
awarded | Supporter |
|
Apr 29 |
awarded | Student |
|
Apr 29 |
asked | Can I have my shell history record how wildcards expanded? |
|
Apr 27 |
comment |
Forcing an 'added' alias to every command If you're using zsh there is an even better way to do it. The REPORTTIME environment variable when set will output the execution time info (as if you had run the command with 'time' in front of it) for any command taking longer than $REPORTTIME seconds. Just set it to 0 and it should tell you the time for every command, with the user/sys breakdown to boot. |