08-06-2019
su should not allow a regular user to start a shell or process for another user without a password. Only root user can do that.
8 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
Hello,
I love the service. My username is Jmt. Can I change that to WebKruncher?
Thanks,
-Jmt
WebKruncher.com - sole proprietor. (1 Reply)
Discussion started by: Jmt
1 Replies
2. Forum Support Area for Unregistered Users & Account Problems
I am on several other Forums under the handle of FloridaBD and therefore
would like to request that my user name here on Unix forums be changed from
SunBurntYux
to FloridaBSD
Thanks. (1 Reply)
Discussion started by: SunBurntYux
1 Replies
3. Shell Programming and Scripting
Hi all,
I am trying to eject the cdrom from a livecd after certain stage...
Now assuming that it is possible to eject,please consider my issue!!!
The OS boots into a regular user by default...so i am unable to use the eject command to push out the drive...
However if i try pfexec eject it... (3 Replies)
Discussion started by: wrapster
3 Replies
4. UNIX for Dummies Questions & Answers
Hi, I was wondering how to change the prompt for my ssh login. At the moment it is like
user>
while I'd like it to be as
user@host>
It is in the .bash_profile or .ssh ??? Thanks (2 Replies)
Discussion started by: pmasterkim
2 Replies
5. Shell Programming and Scripting
Hi,
I have to change many times user in a script.
With the command su userName I receive the request for password. I need to open a session with another user I would put the password at the beginning.
How can I do it?
Thanks, bye bye.
---------- Post updated 22-04-10 at 10:58 AM ----------... (9 Replies)
Discussion started by: abdujaparov
9 Replies
6. Solaris
Hi all
i am using solaris 10, i am creating user with
useradd -d/home/user -m -s /bin/sh user
user is created with in the following path
/export/home/user (auto mount)
i need the user to be created like this
(/home as default home directory )
useradd -d /home/user -m -s /bin/sh... (2 Replies)
Discussion started by: kalyankalyan
2 Replies
7. Red Hat
Dear Experts,
I'm currently working on a Red Hat Linux env. I have been working in AIX. My user is set to use SH default so when it logs in, we have to manually csh to do few things. I know you can change this in AIX using smitty tool. is there any similar too in LINUX that can change it?
... (7 Replies)
Discussion started by: Afi_Linux
7 Replies
8. AIX
If I create a new user id test:
mkuser id=400 test
then I want it to LDAP user:
chuser -R LDAP SYSTEM=LDAP registry=LDAP test
It shows:
3004-687 User "test" does not exist.
How to do? (4 Replies)
Discussion started by: rainbow_bean
4 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