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 REDHAT
pam_xauth
pam_xauth(8) System Administrator's Manual pam_xauth(8)NAME
pam_xauth - forward xauth keys between users
SYNOPSIS
session optional /lib/security/pam_xauth.so arguments
DESCRIPTION
pam_xauth.so is designed to forward xauth keys (sometimes referred to as "cookies") between users.
Without pam_xauth, when xauth is enabled and a user uses the su command to assume another user's priviledges, that user is no longer able
to access the original user's X display because the new user does not have the key needed to access the display. pam_xauth solves the
problem by forwarding the key from the user running su (the source user) to the user whose identity the source user is assuming (the target
user) when the session is created, and destroying the key when the session is torn down.
This means, for example, that when you run su from an xterm sesssion, you will be able to run X programs without explicitly dealing with
the xauth command or ~/.Xauthority files.
pam_xauth will only forward keys if xauth can list a key connected to the $DISPLAY environment variable.
Primitive access control is provided by ~/.xauth/export in the invoking user's home directory and ~/.xauth/import in the target user's home
directory.
If a user has a ~/.xauth/import file, the user will only receive cookies from users listed in the file. If there is no ~/.xauth/import
file, the user will accept cookies from any other user.
If a user has a .xauth/export file, the user will only forward cookies to users listed in the file. If there is no ~/.xauth/export file,
and the invoking user is not root, the user will forward cookies to any other user. If there is no ~/.xauth/export file, and the invoking
user is root, the user will not forward cookies to other users.
Both the import and export files support wildcards (such as *). Both the import and export files can be empty, signifying that no users
are allowed.
ARGUMENTS
debug Turns on debugging messages sent to syslog.
xauthpath=/usr/X11R6/bin/xauth
Specify the path the xauth program (the default is /usr/X11R6/bin/xauth).
IMPLEMENTATION DETAILS
pam_xauth will work only if it is used from a setuid application in which the getuid() call returns the id of the user running the applica-
tion, and for which PAM can supply the name of the account that the user is attempting to assume. The typical application of this type is
su. The application must call both pam_open_session() and pam_close_session() with the ruid set to the uid of the calling user and the
euid set to root, and must have provided as the PAM_USER item the name of the target user.
pam_xauth calls xauth as the source user to extract the key for $DISPLAY, then calls xauth as the target user to merge the key into the a
temporary database and later remove the database.
pam_xauth cannot be told not to remove the keys when the session is closed.
SEE ALSO
/usr/share/doc/pam*/html/index.html
FILES
~/.xauth/import ~/.xauth/export
BUGS
Let's hope not, but if you find any, please report them via the "Bug Track" link at http://bugzilla.redhat.com/bugzilla/
AUTHOR
Nalin Dahyabhai <nalin@redhat.com>, based on original version by Michael K. Johnson <johnsonm@redhat.com>
Red Hat Linux 2001/9/27 pam_xauth(8)