08-02-2011
Well, the user is writing shell history, but it wraps, and the user can destroy it, since they can write it. That is why I mentioned a syslog(), which sends off a message not recallable. I change my HISTFILE and HISTSIZE for more recall not deleted, and back up HISTFILE so I can recall more. But it is almost impossible to track a UNIX user's every execution unless you truss/tusc/strace init or the like. You might do it with a modified /lib/libc.so, if everyone uses the dynamic link. You are really talking about proprietary features added to UNIX. Even then, one might download static binaries and run them.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi
As the title descibes I wish to create an excel spreadsheet which lists all directories in full allong with the users, groups and rights.
I have not used Perl scripts before so I'm a little lost on this on.
Cheers (0 Replies)
Discussion started by: MacLon
0 Replies
2. UNIX for Advanced & Expert Users
Hi,
Is there any way to view process history. Suppose I had killed a few procs yesterday and now I want to see what were the procs that were running yesterday? (2 Replies)
Discussion started by: King Nothing
2 Replies
3. Shell Programming and Scripting
Hello,
I am new to Unix and shell scripting. I am trying to find unowned files and groups on my servers. I know, i could use the below command to find it on individual server.
#find / -nouser -o -nogroup -print
But I was wondering, if someone could help with a shell script so that I can... (2 Replies)
Discussion started by: ut916
2 Replies
4. Shell Programming and Scripting
Well, sudo is a great tool for delegating permissions among admins. But, it's really hard to find a great tool which would give an interactive way of editing /etc/sudoers file. Now, when I say "editing", I really refer to add new groups, users, aliases in the /etc/sudoers file. visudo is great... (2 Replies)
Discussion started by: admin_xor
2 Replies
5. UNIX for Advanced & Expert Users
Hi all,
My need is :
1. To know who , when , which command used.
2. Local user should not delete this information.
I mean , with an example , i can say
i have a user user1
i need to give all the following permissions to user1, :
a. A specific directory other than his home... (3 Replies)
Discussion started by: linuxadmin
3 Replies
6. Shell Programming and Scripting
I admit I am terrible with scripting, so when I was asked to store users' command history lines and zip them on monthly basis what I did was to create a file "user_history_Feb" with the following contents:
Part A
# more user_history_Feb
cp -p /var/log/user_history/*history... (6 Replies)
Discussion started by: hedkandi
6 Replies
7. UNIX for Dummies Questions & Answers
Hi all,
My need is :
1. To know who , when , which command used.
2. Local user should not delete this information.
I mean , with an example , i can say
i have a user user1
i need to give all the following permissions to user1, :
a. A specific directory other than his home... (1 Reply)
Discussion started by: sriky86
1 Replies
8. Shell Programming and Scripting
Hi all. I need a shell script that can, in short, read through a text file line by line and create a new user in Ubuntu, as well as assign that user to a group. The format of the text file is not important but preferably: 'username:group'. I don't have much programming knowledge no matter shell... (3 Replies)
Discussion started by: LewisWeekly
3 Replies
9. UNIX for Beginners Questions & Answers
Hi Team,
I got a requirement to send a mail to the individual users of a unix server about their respective groups. can some one help me to provide the script as I am unable to write that.
I tried with below lines but I come out with errors.
cat /etc/passwd | awk -F':' '{ print $1}' |... (6 Replies)
Discussion started by: harshabag
6 Replies
10. Shell Programming and Scripting
I'm exploring OpenBSD and want to stick to its default shell, which is ksh. My goal is for my regular user ("bruno") and root user to have a shared history file. However, it seems that when running as root, ksh refuses to write to a HISTFILE that is owned by non-root user. This illustrates the... (3 Replies)
Discussion started by: DevuanFan
3 Replies
LEARN ABOUT DEBIAN
calife
CALIFE(1) BSD General Commands Manual CALIFE(1)
NAME
calife -- becomes root (or another user) legally.
SYNOPSIS
calife [-] [login]
or
... [-] [login] for some sites (check with your administrator).
DESCRIPTION
Calife requests user's own password for becoming login (or root, if no login is provided), and switches to that user and group ID after veri-
fying proper rights to do so. A shell is then executed. If calife is executed by root, no password is requested and a shell with the appro-
priate user ID is executed.
The invoked shell is the user's own except when a shell is specified in the configuration file calife.auth.
If ``-'' is specified on the command line, user's profile files are read as if it was a login shell.
This is not the traditional behavior of su.
Only users specified in calife.auth can use calife to become another one with this method.
You can specify in the calife.auth file the list of logins allowed for users when using calife. See calife.auth(5) for more details.
calife.auth is installed as /etc/calife.auth.
FILES
/etc/calife.auth List of users authorized to use calife and the users they can become.
/etc/calife.out This script is executed just after getting out of calife.
SEE ALSO
su(1), calife.auth(5), group(5), environ(7)
ENVIRONMENT
The original environment is kept. This is not a security problem as you have to be yourself at login (i.e. it does not have the same security
implications as in su(1) ).
Environment variables used by calife:
HOME Default home directory of real user ID.
PATH Default search path of real user ID unless modified as specified above.
TERM Provides terminal type which may be retained for the substituted user ID.
USER The user ID is always the effective ID (the target user ID) after an su unless the user ID is 0 (root).
BUGS
The MD5-based crypt(3) function is slower and probably stronger than the DES-based one but it is usable only among FreeBSD 2.0+ systems.
HISTORY
A calife command appeared in DG/UX, written for Antenne 2 in 1991. It has evolved considerably since this period with more OS support, user
lists handling and improved logging.
PAM support was introduced in 2005 to port it to MacOS X variants (Panther and up).
AUTHOR
Ollivier Robert <roberto@keltia.freenix.fr>
BSD
September 25, 1994 BSD