06-28-2011
yes i am aware of sudo. i am using sudo in specific cases where users need to run a script or command that requires root access.however i need just 2 users to have root access "by default". i mean without using sudo. i wanted to see if there is a way to create users with root access without the need of using sudo. sudo is good but if you have users that can be trusted in using root user then sudo can be pretty annoying and frustrating.the problem is that these users are not considered as system administrators thats why i wanted to create different user than root but with root access.if sudo is the only alternative way then i guess i cannot avoid it.thank you for your help
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi All,
Oracle 8.0 database is running on SCO-UNIXWARE 7.0 Operating system. Some how ORACLLE DATABASE has crashed. After rebooting the PC only the SUPER USER could login. No other user is able to login.
we need ORACLE user to start the DATABASE again.
It is asking for the password, after... (2 Replies)
Discussion started by: konda
2 Replies
2. HP-UX
Hi All,
I m facing a problem that, i m not able to login as root user on cde on hp-ux 11.00, i can login as root on commond line as well as telnet. Thanks in Advance for help.
Regards,
Awadhesh (1 Reply)
Discussion started by: Awadhesh
1 Replies
3. Linux
Hi,
I am having small query and wheather it is possible ? that user can transfer the files using ftp client examples (filezilla) , but he can not use putty to login using ftp and run the commands,
Regards,
Manoj (2 Replies)
Discussion started by: manoj.solaris
2 Replies
4. Solaris
Hi to All,
I have configured telnet service in my server but am not able to login with root user in Linux Servers.
For that what can i do ?
Please help me
Thanks in Advance. (1 Reply)
Discussion started by: Sharath Kumar
1 Replies
5. Solaris
I am running 5.10 Generic_120011-14
Sunblade 1500
I have one client that was working fine in a training environment. Then this week the user is unable to login as the user that is created by default. The students do not have access to root to change system files or user accounts. This is... (11 Replies)
Discussion started by: deaconf19
11 Replies
6. Debian
hello friends,
one user is created named "user1"
I login as "user1" . Now when i do "su -" to be root user I have to give password for root .
Is there any way through which we can skip giving the password to root.
i.e.
user1@work:~$ su -
Password: xxxxxx
work:~$
I don't want that... (1 Reply)
Discussion started by: pradeepreddy
1 Replies
7. UNIX for Dummies Questions & Answers
Hi folks.
our developer had a root user and he changed some settings about root user. We have not known what he changed.
There is an oracle user, we can login to oracle, no problem. But when we try to login to root user we are getting this error :
$ su root
Password:
bash:... (9 Replies)
Discussion started by: futi
9 Replies
8. Shell Programming and Scripting
hello all,
if we haven't set a password to root user, how can we login as root user in konsole by using su? is it necessary to set password for root to login as root user?how can we set password to root user? (6 Replies)
Discussion started by: aarathy
6 Replies
9. Shell Programming and Scripting
Hi Every body,
I would need a shell script program to login as different user and perform some copy commands in the script.
example: Supppose ora_toms is the active user
ora_toms should be able to run a script where user: ftptomsp pass: XXX should login through and run the commands
... (9 Replies)
Discussion started by: ujjwal27
9 Replies
10. UNIX for Advanced & Expert Users
Anyone has met the error following:-
1. Only root could login Redhat
2. Trying su another user by root, the error will be
su: warning: cannot change directory to /home/user: permission denied
su: /bin/bash: permission denied
3. I have checked the permission of the folder given and even... (2 Replies)
Discussion started by: jc0616
2 Replies
LEARN ABOUT CENTOS
pam_ssh_agent_auth
pam_ssh_agent_auth(8) PAM pam_ssh_agent_auth(8)
PAM_SSH_AGENT_AUTH
This module provides authentication via ssh-agent. If an ssh-agent listening at SSH_AUTH_SOCK can successfully authenticate that it has
the secret key for a public key in the specified file, authentication is granted, otherwise authentication fails.
SUMMARY
/etc/pam.d/sudo: auth sufficient pam_ssh_agent_auth.so file=/etc/security/authorized_keys
/etc/sudoers:
Defaults env_keep += "SSH_AUTH_SOCK"
This configuration would permit anyone who has an SSH_AUTH_SOCK that manages the private key matching a public key in
/etc/security/authorized_keys to execute sudo without having to enter a password. Note that the ssh-agent listening to SSH_AUTH_SOCK can
either be local, or forwarded.
Unlike NOPASSWD, this still requires an authentication, it's just that the authentication is provided by ssh-agent, and not password entry.
ARGUMENTS
file=<path to authorized_keys>
Specify the path to the authorized_keys file(s) you would like to use for authentication. Subject to tilde and % EXPANSIONS (below)
allow_user_owned_authorized_keys_file
A flag which enables authorized_keys files to be owned by the invoking user, instead of root. This flag is enabled automatically
whenever the expansions %h or ~ are used.
debug
A flag which enables verbose logging
sudo_service_name=<service name you compiled sudo to use>
(when compiled with --enable-sudo-hack)
Specify the service name to use to identify the service "sudo". When the PAM_SERVICE identifier matches this string, and if PAM_RUSER
is not set, pam_ssh_agent_auth will attempt to identify the calling user from the environment variable SUDO_USER.
This defaults to "sudo".
EXPANSIONS
~ -- same as in shells, a user's Home directory
Automatically enables allow_user_owned_authorized_keys_file if used in the context of ~/. If used as ~user/, it would expect the file
to be owned by 'user', unless you explicitely set allow_user_owned_authorized_keys_file
%h -- User's Home directory
Automatically enables allow_user_owned_authorized_keys_file
%H -- The short-hostname
%u -- Username
%f -- FQDN
EXAMPLES
in /etc/pam.d/sudo
"auth sufficient pam_ssh_agent_auth.so file=~/.ssh/authorized_keys"
The default .ssh/authorized_keys file in a user's home-directory
"auth sufficient pam_ssh_agent_auth.so file=%h/.ssh/authorized_keys"
Same as above.
"auth sufficient pam_ssh_agent_auth.so file=~fred/.ssh/authorized_keys"
If the home-directory of user 'fred' was /home/fred, this would expand to /home/fred/.ssh/authorized_keys. In this case, we have not
specified allow_user_owned_authorized_keys_file, so this file must be owned by 'fred'.
"auth sufficient pam_ssh_agent_auth.so file=/secure/%H/%u/authorized_keys allow_user_owned_authorized_keys_file"
On a host named foobar.baz.com, and a user named fred, would expand to /secure/foobar/fred/authorized_keys. In this case, we specified
allow_user_owned_authorized_keys_file, so fred would be able to manage that authorized_keys file himself.
"auth sufficient pam_ssh_agent_auth.so file=/secure/%f/%u/authorized_keys"
On a host named foobar.baz.com, and a user named fred, would expand to /secure/foobar.baz.com/fred/authorized_keys. In this case, we
have not specified allow_user_owned_authorized_keys_file, so this file must be owned by root.
v0.8 2009-08-09 pam_ssh_agent_auth(8)