The account userA can directly issue:-
..... indeed anything you can think of. Yes, it might be logged via syslog, but they can edit the output to cover their tracks. You effectively have userA as a full privilege account. What does userA actually need to do?
If you are nervous of (and should be) giving out commands such as cp, rm, mv, vi, ftp etc. (especially as you can escape to a shell in the latter two) because you can then attack everything, then script up what is allowed and give them access to sudo-execute (not alter) the script meaning that they don't have direct access to the commands.
Give away as little as possible, after all it's you that will have to put it all back together again if they break something (intentionally or in error) if you still have a job. I don't want this to be scary, but would you give a local builder full access to your bank account to and trust them only to withdraw what they are owed?
I just need to know what should be done on a login user so that no one can access it except through sudo
i.e.
telnet server
login: user
NO ACCESS
telnet server
login: mylogin
sudo - user <any command>
ACCESS GRANTED
thanks (0 Replies)
Hi All,
I got lots of request with sudo, a manager request, verbal command, do this and do that.
The problem with this kind of request is when I added that script and that. It will not be perfect, it's because I can't verify the userid sudo access, I can't reset their password as well, I... (2 Replies)
I have installed sudo on AIX 6100-04 and want to know how do I set it up for a user to be able to run only some commands? I want to give the user the rights to only cd to certain directories and run the ls command to name a few? Are there any issues with running sudo when the user is forced to... (2 Replies)
Hello All,
I want to create a script that will do ONLY su to any user on the server with hpadmin login using sudo. Can anyone let me know how can it do it.
Regards
Ankit (1 Reply)
I'm actually working with a Ubuntu-System here and have a question about executing a command with 'sudo'.
I tried and got a error message like "not allowed".
After this I logged in with 'sudo -s' and typed the command without 'sudo'. This worked well.
Can please somebody explain me this... (0 Replies)
Linux ubuntu 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
Hi Folks,
Please help me. I am bit struck here.
Here is the OS info.
Linux ubuntu 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
I have a... (17 Replies)
I want to give root access to a user called denielr on server - tsprd01, but do not want to share root password. I have sudoers configured already.
He should have all access equal to root. I made this entry in /etc/sudoers, but it is not working
denielr tsprd01 =(root) NOPASSWD: ALL
I tried to... (2 Replies)
Install the sudo pkg SFWsudo.tar
bash#tar -xvf SFWsudo.tar
bash#pkgadd -d . SFWsudo
path may be /opt/sfw/bin
Make entry the user name in sudoer file
path of the sudoer file
/opt/sfw/etc/sudoers
check with the below command as a user (not as a root user)
user1$... (1 Reply)
Hi,
I have given access to user mwadmin in shudders file as :
mwadmin ALL:NOPASSWD:/www/* /usr/* /opt/*
However, not able to execute below command:
sudo mkdir -p /usr/test
password for mwadmin:
Sorry, user mwadmin is not allowed to execute '/bin/mkdir -p /usr/test' as root.
... (4 Replies)
I have similar issue as mentioned in
167174-how-run-script-using-batch-file.html
It works good, but the control is not coming back to source i tried adding exit to remote script.
Thanks,
Suresh (0 Replies)
Discussion started by: snsuresh
0 Replies
LEARN ABOUT OSX
networkd
networkd(8) BSD System Manager's Manual networkd(8)NAME
networkd -- network daemon.
SYNOPSIS
networkd
DESCRIPTION
networkd is a launch-on-demand daemon that performs opreations on behalf of code in libystem_network, a component of libSystem.
networkd has no user-specifiable command-line argument, and users should not run networkd manually.
LOGGING
There are several methods with which to examine networkd's internal state for debugging and diagnostic purposes. The syslog(1) logging levels
map as follows:
Error - Error messages
Warning - Non-fatal concerns
Notice - Internal state messages
Info - Informational messages
By default, only log level Notice through Error is logged.
Syslog may be used to modify the mask which logging levels are logged. For example, to enable log levels Emergency - Debug :
% sudo syslog -c networkd -d
The networkd settings file may also be used to change the log level. This method will add some additional logging that may be missing using
the syslog technique listed above. This method is also persistent across runs of networkd For example, to enable log levels Emergency (1)
through Debug (7):
% sudo defaults write /Library/Preferences/com.apple.networkd networkd_log_level -int 7
The networkd settings file may also be used to change the log level for code in libsystem_network. For example, to enable log levels Emer-
gency (1) through Debug (7) for libsystem_network code:
% sudo defaults write /Library/Preferences/com.apple.networkd libnetcore_log_level -int 7
A SIGINFO signal will dump a snapshot summary of the internal state to the system log at log level NOTICE :
% sudo killall -INFO networkd
FILES
/usr/libexec/networkd
The binary.
/System/Library/LaunchDaemons/com.apple.networkd.plist
The launchd.plist(5) controlling the networkd job.
/Library/Preferences/com.apple.networkd.plist
An optional preferences file read by networkd.
BUGS
networkd bugs are tracked in Apple Radar component "networkd".
HISTORY
networkd first appeared in Mac OS X 10.7.
SEE ALSO networkd_privileged(8), syslogd(8), launchd.plist(5)Darwin June 2, 2019 Darwin