topic Re: security in .sh_history in Operating System - HP-UX

security in .sh_history

Daniel Piedras_1 — Wed, 09 Feb 2005 17:26:39 GMT

the question is that the user doesn't see what you/he/she/it register in the .sh_history, and that single [root] could see this.

Re: security in .sh_history

Steven E. Protter — Wed, 09 Feb 2005 17:46:09 GMT

Kind of a cryptic post. No question mark either.

root can see any file the person logged on as root wants. Thats a fact that does not change.

The umask parmeter controls default permissions when a new file is created. If you set that in /etc/profile when new users are created, permissions will be the way you want on .sh_history

chmod 700 .sh_history so long as the user owns it.

If root owns it, permissions need to be more flexible.

SEP

Re: security in .sh_history

Florian Heigl (new acc) — Wed, 09 Feb 2005 17:49:43 GMT

set it
-w------ user:staff .sh_history

but - this won't get You anywhere. The history works only as long as it is *readable*!

but You can have a single history for every user - I think this is the way You should go.

the variable is $HISTFILE and You could use /etc/profile to set it by e.g.

WHO=`whoami`
HISTFILE="~$WHO/.sh_history"
HISTSIZE=2048

touch and chown it for every user to come.

Re: security in .sh_history

Daniel Piedras_1 — Wed, 09 Feb 2005 19:33:18 GMT

Thanks

Regards

Re: security in .sh_history

Andrew Cowan — Thu, 10 Feb 2005 02:27:14 GMT

Do you mean that you want a new ".sh_history" file everytime that someone logs-in/su's to root? If this is the case simply add a few lines to your ".profile" to change the name of the ".sh_history" to do something like append the date and time, or the IP-Address or username of the user.
You also add a "trap" to call a file such as ".kshexit" that moves or renames the file so it can be stored for auditing purposes.

There are a lot of projects knocking around that are trying to create a kind of flight-recorder for root's actions, however there can be serious privacy issues surrounding this aproach, so make sure that it complies with your local legislation.

Re: security in .sh_history

TEC-HP — Thu, 10 Feb 2005 02:57:24 GMT

Hi Daniel,

Think we are looking for the same: Command Auditting http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=805145

apearantly there is a possibility to recompile bash (don't know yet how) to log all interactive commands into a sepparate file. But then you have the support issue and of course as Andrew stated: legislation