Here’s an even easier way: just run xterm &.
#How to install nedit to use in command prompt how to#
Almost anybody can work out how to work around it in a few minutes. It is totally impossible to enforce command recording through either shell history or script logging. It might be noticed as suspicious activity, but I can never be caught issuing the rm commands. But it does not report commands that are inside other scripts.Īnd it will also record the fact that I deleted the foo file.īut the session logs will NEVER record the rm commands themselves. This "script" command records what was typed at the terminal, and it records what goes to stdout and stderr at the terminal. But, the commands INSIDE the file foo will not be recorded. The fact I ran the script will be recorded too. The point is, I could edit a command file foo that contains:Īnd that edit does not show up in the script, because it is not part of the session. I know the commands I *typed* in the session will be reported in the script file. I could probably find another 20 ways if I tried a little harder. Then they arrange not even to be in the state when the files disappear. They write a script, and make an at job to run it and then delete the script. They FTP to the local machine and remove it in FTP. inode 45234 -exec rm " ", having previously found the inode through the appropriate ls option. They write a script containing aliases that delete files, source it, and run the alias. They run a shell command from inside vi with :! rm whatever. They write a C, Java, C++, Python, Perl etc. They write an awk script that uses system() to delete files, and then run it. They write a shell script that deletes files, and then run it. So, it wouldn’t catch any of the following: That only logs the commands that they type on the current terminal. bash_history file located in their home dirs
0 kommentar(er)
