History is certainly useless since it's under control of the user. I looked in my bash book at saw:
Quote:
...HISTCONTROL variable. If set to ignorespace, any commands that you type that start with a space won't appear in the history.
And there are many other ways to defeat history including typing "sh" and running a bourne shell for awhile.
I hate to be a party pooper, but accounting is also easily defeated. But why bother? Suppose your accounting records shows that I did:
Code:
vi perderabo.c
cc perderabo.c -o perderabo
./perderabo
rm perderabo.c perderabo
OK, now what did I do?
Some versions of unix have C2 level security features. You can configure them to track every system call invoked by every user. This puts a nasty load of the system though. Short of this, you aren't going to be able to reliably track what users do.
During the course of the session before I logout I see some of the commands listed from my previous session but not from my current session and after I logout and log back in I see the commands which I ran before logging out.
Does the .bash_history stay in the buffer or someplace else then?
... (2 Replies)
Dear All,
I am creating users on our servers. the .bash_history supposed to store all the commands entered by the user. My question is, how can I prevent the user himself from editing or viewing this file?
I have tried chaning the owner of the .bash_history to be the root user but... (5 Replies)
Hi Experts,
I know my question would be strange but i need to understand how the .bash_history file is logging user actions (the mechanism) and if possible modify it to include also the date/time of every action done by the user.
Sample file:
# more .bash_history
ssh <IP address> -l axadmin... (3 Replies)
Hi - user commands are written in . bash_history of that user when he logs out. my bash_history file shows. not sure what that number means
#1329618972
ls -la
#1329618978
ls
#1329618980
ls -la
my bash_profile looks like this
PATH=$PATH:$HOME/bin
export PATH
export... (3 Replies)
rm -rf .bash_history some one ran rm -rf .bash_history on my Linux server(SUSE),I can see this command being run in current history, but I want the OLD history as well,can I recover the old history back. (9 Replies)
Hi would like to ask if there is anyway to display .bash_history with timestamp using shell script?
i know that you should use history command with HISTTIMEFORMAT="%d/%m/%y %T " to display it in terminal but it does not work when i use it on shell script. It seem that you can't run history... (1 Reply)
I am using the bash shell.
When I view my recent command history using the "history" command from the prompt, it only shows me the commands starting at #928.
The commands I need are earlier than that, but I can't figure out how to make the other 927 display.
They are in my .bash_history... (1 Reply)
Discussion started by: Twinklefingers
1 Replies
LEARN ABOUT XFREE86
chsh
CHSH(1) User Commands CHSH(1)NAME
chsh - change login shell
SYNOPSIS
chsh [options] [LOGIN]
DESCRIPTION
The chsh command changes the user login shell. This determines the name of the user's initial login command. A normal user may only change
the login shell for her own account; the superuser may change the login shell for any account.
OPTIONS
The options which apply to the chsh command are:
-h, --help
Display help message and exit.
-R, --root CHROOT_DIR
Apply changes in the CHROOT_DIR directory and use the configuration files from the CHROOT_DIR directory.
-s, --shell SHELL
The name of the user's new login shell. Setting this field to blank causes the system to select the default login shell.
If the -s option is not selected, chsh operates in an interactive fashion, prompting the user with the current login shell. Enter the new
value to change the shell, or leave the line blank to use the current one. The current shell is displayed between a pair of [ ] marks.
NOTE
The only restriction placed on the login shell is that the command name must be listed in /etc/shells, unless the invoker is the superuser,
and then any value may be added. An account with a restricted login shell may not change her login shell. For this reason, placing /bin/rsh
in /etc/shells is discouraged since accidentally changing to a restricted shell would prevent the user from ever changing her login shell
back to its original value.
FILES
/etc/passwd
User account information.
/etc/shells
List of valid login shells.
/etc/login.defs
Shadow password suite configuration.
SEE ALSO chfn(1), login.defs(5), passwd(5).
shadow-utils 4.5 01/25/2018 CHSH(1)