The applications that I want to run are on Linux Server [NFS] and the client machines [CIFS] that are having problem in locking the .Xauthority files are Macs which share the same domain as that of client solaris machine. i.e. The home directory of particular user on Solaris & the home directory of that user on Mac have same contents.
When I ssh -X from Solaris to the server, everything works fine, no error messages.
When I ssh -X from MACs to the server, I get the following warning messages.
/usr/X/bin/xauth is the path on the server. If I try to break the lock by sudo /usr/X/bin/xauth -b quit, I get the following error
When I ssh -X from any my MacBookPro to the server,
I have checked sshd_config on both the server and the Mac clients, there is nothing that seems wrong, but if you guys have insights then please share.
---
Deleting .Xauthority files work, but thats not a good solution. I mean, everytime I have to run any X forwarding application I have to delete the .Xauthority file
I have a set of scripts to do software releases to remote machines which uses ftp. I'm having a problem getting 'lost connection' messages.
What I wanted to ask is, does ftp employ some sort of file locking if two ftp processes are trying to copy the same file at the same time? & if so could... (2 Replies)
Hi,
Simple question but I just need to confirm the answer:
If two or more processes attempt to move the same file at exactly the same time, will unix internal file locking allow only one of the processes to access the file?
Many thanks
Helen :) (2 Replies)
We want to lock a file, during a program(pgm1) execution(until the execution of the program is completed), so that other program(pgm2) can't read/edit that file, until execution of earlier program(pgm1) is completed. How can this be achieved thru shell scripting...
we tried chmod +l option, but... (1 Reply)
Folks,
I am having a minor problem on a new AIX install. I have AIX installed in and LPAR on a p550 and everything works fine with the exception of users who log in with ssh.
It seems that when a user has X11 forwarding enabled in their ssh client and they connect to the server, logins hang.... (3 Replies)
how do i implement file locking in unix?
example if i want to update a file, i would like to use file locking. how do i implement it?
i am using shell script
thanks (3 Replies)
how to ensure all files are being locked while updateing some files?
example when i want to update the password and shadow file in unix. how do i implement file locking??
please advice
thanks (2 Replies)
i am working on a device runnin on linux....i have configured the samba server in the device such that my windows PC can access a shared folder in the device. Also in the device i am runnin some programs which access the files in this shared folder. What i want to know is whether there is any way i... (1 Reply)
Discussion started by: abhinx
1 Replies
LEARN ABOUT LINUX
pam_xauth
PAM_XAUTH(8) Linux-PAM Manual PAM_XAUTH(8)NAME
pam_xauth - PAM module to forward xauth keys between users
SYNOPSIS
pam_xauth.so [debug] [xauthpath=/path/to/xauth] [systemuser=UID] [targetuser=UID]
DESCRIPTION
The pam_xauth PAM module 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(1) command to assume another user's privileges, 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(1) from an xterm session, you will be able to run X programs without explicitly dealing with
the xauth(1) 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.
OPTIONS
debug
Print debug information.
xauthpath=/path/to/xauth
Specify the path the xauth program (it is expected in /usr/X11R6/bin/xauth, /usr/bin/xauth, or /usr/bin/X11/xauth by default).
systemuser=UID
Specify the highest UID which will be assumed to belong to a "system" user. pam_xauth will refuse to forward credentials to users with
UID less than or equal to this number, except for root and the "targetuser", if specified.
targetuser=UID
Specify a single target UID which is exempt from the systemuser check.
MODULE TYPES PROVIDED
Only the session type is provided.
RETURN VALUES
PAM_BUF_ERR
Memory buffer error.
PAM_PERM_DENIED
Permission denied by import/export file.
PAM_SESSION_ERR
Cannot determine user name, UID or access users home directory.
PAM_SUCCESS
Success.
PAM_USER_UNKNOWN
User not known.
EXAMPLES
Add the following line to /etc/pam.d/su to forward xauth keys between users when calling su:
session optional pam_xauth.so
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
application, 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(1). 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(1) 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 to not remove the keys when the session is closed.
FILES
~/.xauth/import
XXX
~/.xauth/export
XXX
SEE ALSO pam.conf(5), pam.d(5), pam(7)AUTHOR
pam_xauth was written by Nalin Dahyabhai <nalin@redhat.com>, based on original version by Michael K. Johnson <johnsonm@redhat.com>.
Linux-PAM Manual 06/04/2011 PAM_XAUTH(8)