to enable Rexec you will need to comment out one line in the file /etc/pam.d/rexec. Here is a sample of the file *Your file might be diffrent:
After this file is modified, rexec will be enabled.
**Note: If your /etc/pam.d/rexec file contains a line referring to
the pam_securetty.so module, you will not be able to rexec as root..!!
This User Gave Thanks to killerserv For This Post:
In http://forums.unix.com/showthread.php?threadid=391
there is one statement called expect.
but when I issue command whereis expect, respond from o/s only EXPECT: (only one world).
I try to find it at /usr/bin, no expect statement there ?
is it default unix o/s command ?
I am using AIX on... (1 Reply)
Hi, all.
Could some one help me please with one problem?
In one process (on aix) I should run some remote scripts on other server via rexec.
Some scripts should be run on server1 under useridA, and some scripts should be run on the same server under useridB.
I specified in .netrc... (10 Replies)
Hi UNIX gurus.....
have a doubt..can i run a script in a remote machine by using something like
rexec add.corp.afg.com /aa/ss/remtescript
I dont want to use the rsh command due to some security issues.
thanx,
rahul26 :) (2 Replies)
Hi folks!
my client uses an winapplication which is launching shell-scripts remotely on a HP-Unix Machine via Rexec.
The application-configuration is launching the script (which is in the home directory of connecting user) like:
rexec host user pass shell.sh
So far so good, everything... (3 Replies)
how do i/is there a way to return the exit code from the remote host?
echo $? from the local host only gives 0, if the rexec command itself executes successfully. But what if in the case of the remote command failiing? echo $? on the localhost still gives 0, but I'm interested in the exit code... (4 Replies)
Rexec executes commands one at a time on a remote host. The rexec command provides an automatic login feature by checking for a $HOME/.netrc file. User and password are stored
in $HOME/.netrc.
I would like to log on to another host and execute a script/command but not using $HOME/.netrc file,... (4 Replies)
Hi Team,
I am executing some ksh scripts which inturn calls java files in AIX Environment. We have installed java6_64 which is in .profile. But when we execute from rexec its taking path from some different place that does not have java in $PATH variable. Can you please help me find out which... (2 Replies)
Hi,
I am trying to enable rexec to automate certain tasks(it has to be rexec, not ssh or any other due to the system environment), so after switching to linux, I followed the certain instructions that were laid out in the web.
My operating system is fedora 17, so I first installed the... (1 Reply)
Hi all,
I´m replacing an old linux enterprise redhat 4.5 by a new one linux enterprise redhat 6.
In both I use rexec as a communication between the front end and the user.
In the old one, when the user connects, the communication establishes quickly (less than 3 sec). But in the new one, the... (1 Reply)
Discussion started by: mig28mx
1 Replies
LEARN ABOUT REDHAT
pam_timestamp
pam_timestamp(8) System Administrator's Manual pam_timestamp(8)NAME
pam_timestamp - authenticate using cached successful authentication attempts
SYNOPSIS
auth sufficient /lib/security/pam_timestamp.so
session optional /lib/security/pam_timestamp.so
DESCRIPTION
In a nutshell, pam_timestamp caches successful authentication attempts, and allows you to use a recent successful attempt as the basis for
authentication.
When an application opens a session using pam_timestamp, a timestamp file is created in the timestampdir directory for the user. When an
application attempts to authenticate the user, a pam_timestamp will treat a sufficiently- recent timestamp file as grounds for succeeding.
ARGUMENTS
debug turns on debugging via syslog(3).
timestampdir=name
tells pam_timestamp.so where to place and search for timestamp files. This should match the directory configured for sudo(1) in the
sudoers(5) file.
timestamp_timeout=number
tells pam_timestamp.so how long it should treat timestamp files as valid after their last modification date. This should match the
value configured for sudo(1) in the sudoers(5) file.
verbose
attempt to inform the user when access is granted.
EXAMPLE
/etc/pam.d/some-config-tool:
auth sufficient /lib/security/pam_timestamp.so verbose auth required /lib/security/pam_unix.so
session required /lib/security/pam_permit.so session optional /lib/security/pam_timestamp.so
CAVEATS
Users can get confused when they aren't always asked for passwords when running a given program. Some users reflexively begin typing
information before noticing that it's not being asked for.
SEE ALSO pam_timestamp_check(8)BUGS
Let's hope not, but if you find any, please email the author.
AUTHOR
Nalin Dahyabhai <nalin@redhat.com>
Red Hat Linux 2002/02/07 pam_timestamp(8)