Timeline for Create history log per working directory in bash
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 14 at 14:38 | comment | added | CodeMedic | See my answer unix.stackexchange.com/a/794892 which hopefully addresses some of the concerns raised by @Gilles'SO-stopbeingevil' | |
| S Feb 21, 2023 at 16:40 | history | suggested | Miguel Sánchez Villafán | CC BY-SA 4.0 | add usage warning and considerations |
| Feb 19, 2023 at 0:09 | review | Suggested edits | |||
| S Feb 21, 2023 at 16:40 | |||||
| Apr 13, 2017 at 12:37 | history | edited | CommunityBot | replaced http://unix.stackexchange.com/ with https://unix.stackexchange.com/ | |
| Apr 13, 2017 at 12:22 | history | edited | CommunityBot | replaced http://askubuntu.com/ with https://askubuntu.com/ | |
| Aug 25, 2016 at 13:24 | vote | accept | tafelplankje | ||
| Aug 25, 2016 at 13:24 | comment | added | tafelplankje | Great, I didn't think about that, thanks very much. | |
| Aug 24, 2016 at 23:15 | comment | added | Gilles 'SO- stop being evil' | You should note that this configuration is highly dangerous. Sooner or later you're going to leak some confidential commands in a publicly exposed archive or repository. On a multiuser machine, as soon as you change into another user's directory and run a few commands there, they can modify your files and probably gain a backdoor to your account. And other users, or people whose archives you download, can easily trick you into running commands by injecting them into your shell history. | |
| Aug 24, 2016 at 22:31 | history | edited | Gilles 'SO- stop being evil' | CC BY-SA 3.0 | edit history belongs in the edit history, not in the post |
| Aug 24, 2016 at 21:22 | history | edited | Chuck Horowitz | CC BY-SA 3.0 | added 191 characters in body |
| Aug 24, 2016 at 21:00 | review | First posts | |||
| Aug 24, 2016 at 21:14 | |||||
| Aug 24, 2016 at 20:59 | history | answered | Chuck Horowitz | CC BY-SA 3.0 |