After adding the setuid flag to your app you should be able to run the application with a standard user account.
Quote:
setuid and setgid (short for set user ID upon execution and set group ID upon execution, respectively) are Unix access rights flags that allow users to run an executable with the permissions of the executable's owner or group. They are often used to allow users on a computer system to run programs with temporarily elevated privileges in order to perform a specific task. [...] - http://en.wikipedia.org/wiki/Setuid
Hi all,
how can i grant write access to a selective users only with write access to a certain filesystem/directory in solaris 10.
Please help..i tried "fs setacl"...does not seem to work
Please adv..thanks in advance... (4 Replies)
hi
i am new to unix and i have abig task. i have to \run particular commands having root privileges from a non root user. i know sudo is one of the way but i need sum other approach kindly help
Thanks (5 Replies)
hi all,
i want to know y kernel is giving access for multiple users to access a file when one user may be the owner is executing that file. Because other user can manipulate that file when the other user is executing that file, it will give the unexpected result to owner . plz help me... (1 Reply)
Hi to all,
Please, some help over here. IŽll try to be as much clear I can.
In summary my problem is:
I have a PHP application installed in a folder of my domain that reads CSV.txt files from
another folder in my domain and I need to restrict direct access to see and download these CSV.txt... (0 Replies)
I am using SUSE Linux Enterprise Server 10 SP2 (i586) and I had earlier ammended my sudoers file to allow users to become root user with "sudo su - " command
Now I am trying to add multiple users to the sudoers file to run several commands such as restarting the server, restarting the nagios... (9 Replies)
Hi all
I am try NFS on node1 & node2 servers.
On node1, when I am using
# share -F nfs -o rw,anon=0 /abc
On node2, when I am using
# mount -f nfs node1:/abc /a
in /a folder, root user is able to create files but any other user from node2 is not able to create files, please... (1 Reply)
Hi All,
I want to configure samba share permission so that only directory creator/owner has a read and write permission and other users should not have any read/write access to that folder.Will that be possible and how can this be achieved within samba configuration.
Regards,
Sahil (1 Reply)
I need to list users in /etc/passwd with root's GID or UID or /root as home directory
If we have these entries in /etc/passwd
root:x:0:0:root:/root:/bin/bash
rootgooduser1:x:100:100::/home/gooduser1:/bin/bash
baduser1:x:0:300::/home/baduser1:/bin/bash... (6 Replies)
local script:
cat > first.sh
cd /tmp
echo $PWD
echo `whoami`
cd /tmp/123
tar -cvf 789.tar 456
sleep 10
except script:
cat > first
#!/usr/bin/expect
set ip 10.5.15.20
set user "xyz123"
set password "123456"
set script first.sh
spawn sh -c "ssh $user@$ip bash < $script" (1 Reply)
Hi,
We have two LDAP servers. Whenever we get a ticket to reset the password, we login to LDAP primary server and reset the password. For below example, I logged into primary LDAP server and resetting password to john to Welcome123#
We are giving this work to tier-1 team, so that they can reset... (1 Reply)
Discussion started by: ron323232
1 Replies
LEARN ABOUT DEBIAN
ninja
NINJA(8)NINJA(8)NAME
ninja - Privilege escalation detection system for GNU/Linux
SYNOPSIS
ninja filename
DESCRIPTION
Ninja is a privilege escalation detection and prevention system for GNU/Linux hosts. While running, it will monitor process activity on the
local host, and keep track of all processes running as root. If a process is spawned with UID or GID zero (root), ninja will log necessary
information about this process, and optionally kill the process if it was spawned by an unauthorized user.
A "magic" group can be specified, allowing members of this group to run any setuid/setgid root executable.
Individual executables can be whitelisted. Ninja uses a fine grained whitelist that lets you whitelist executables on a group and/or user
basis. This can be used to allow specific groups or individual users access to setuid/setgid root programs, such as su(1) and passwd(1).
CONFIGURATION
Ninja requires a configuration file to run. For more information about the configuration, please refer to the "default.conf" file, located
at "/usr/share/doc/ninja/examples/" in the source tree. There, all the available options are explained in detail.
WHITELIST
The whitelist is a plain text file, containing new-line separated entries. Entries consists of three fields, separated by colons. The
first field is the full path to the executable you wish to whitelist. The second field is a comma separated list of groups that should be
granted access to the executable. The third field is a comma separated list of users.
<executable>:<groups>:<users>
The second or third field can be left empty. Please refer to the example whitlist located in "/usr/share/doc/ninja/examples/".
Remember that it is a good idea to whitelist programs such as passwd(1) and other regular setuid applications that users require access to.
SECURITY
The goal of this application is to be able to detect and stop local, and possibly also remote exploits. It is important to note that ninja
cannot prevent attackers from running exploits, as a successful exploitation only will be detected AFTER the attacker has gained root. How-
ever, when ninja is running with a short scanning cycle, this detection happens nearly immediately. The security lies in the fact that we
stop the attacker before he/she has time to do anything nasty to the system, and it gives us the opportunity to disable the attacker's
shell access, and lock him/her out of the system.
In an ideal environment, ninja should be run together with kernel hardening systems such as grsecurity (www.grsecurity.net) as this will
allow for some protection of the ninja process.
This is not a complete security system. Do not rely on it to keep your system safe.
BUGS
Please let me know if you should stumble across any bugs or other weirdness. I greatly appreciate all bug reports, patches, ideas, sugges-
tions and comments.
LICENSE
Ninja is released under the General Public License (GPL) version 2 or higher.
AUTHOR
Tom Rune Flo <tom@x86.no>
August 2005 NINJA(8)