10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi
I have an ssh 'for' loop script to login and put a key on multiple servers. I need to append a file on each server but the command which works ok from the prompt does not work via the script. I have
cat filename | ssh user@servername "cat >>append.file.name"
I have tried to 'spawn' this in... (0 Replies)
Discussion started by: Grueben
0 Replies
2. Shell Programming and Scripting
Hi
This is my third past and very impressed with previous post replies
Hoping the same for below query
How to find a existing file location and directory location in solaris box (1 Reply)
Discussion started by: buzzme
1 Replies
3. Shell Programming and Scripting
Hi,
I am logging to a linux server through a user "user1" in /home directory.
There is a script in a directory in 'root' for which all permissions are available including the directory. This script when executed creates a file in the directory.
When the script is added to crontab, on... (1 Reply)
Discussion started by: archana.n
1 Replies
4. UNIX for Advanced & Expert Users
Hi
Little background on what I want to achieve and why I do this. I have a RHEL server with users logging in via ssh. I want to start using public keys instead of passwords with ssh. But public key is as good as a rotten tomato if it is unpassphrased and I cannot guarantee that all users will... (4 Replies)
Discussion started by: bortek
4 Replies
5. Shell Programming and Scripting
Create a script that copies files from one specified directory to another specified directory, in the order they were created in the original directory between specified times. Copy the files at a specified interval. (2 Replies)
Discussion started by: allways4u21
2 Replies
6. Red Hat
I am trying to set up ssh/scp to be able to login in w/o using a password. The man pages for ssh and ssh-keygen explain how to do this.
So, using "rsa1" style, I created the public and private keys by way of ssh-keygen, then added the contents of "$HOME/.ssh/identity.pub" to a newly created... (6 Replies)
Discussion started by: mcrouch_2003
6 Replies
7. Shell Programming and Scripting
I am creating public and private key for sftp in ksh.
then copy the name1.pub file into /.ssh/authorized_keys directory in remote server.
Now my question is how to write that script which do not ask me for the password from prompt.
please help.
thanks in advance. (1 Reply)
Discussion started by: rinku
1 Replies
8. Solaris
Hello gurus,
I have question. I have enabled ssh on the servers.
I am planning to change the oracle user's(os user) password. If I change the password will it affect the authorized_keys? Do I need to regenerate it.
Thanks, (2 Replies)
Discussion started by: oracleuser
2 Replies
9. UNIX for Advanced & Expert Users
Hi,
We have around 200 SUN Servers in production environment and I have one box from where I manage all the servers. It's setup such that I can SSH from my box onto all the 200 servers with without supplying password. It is working fine but sometimes we notice the keys getting changed and asking... (1 Reply)
Discussion started by: prvnrk
1 Replies
10. Shell Programming and Scripting
Hi,
We have around 200 SUN Servers in production environment and I have one box from where I manage all the servers. It's setup such that I can SSH from my box onto all the 200 servers with without supplying password. It is working fine but sometimes we notice the keys getting changed and asking... (0 Replies)
Discussion started by: prvnrk
0 Replies
RSSH.CONF(5) Derek D. Martin RSSH.CONF(5)
NAME
/etc/rssh.conf - configuration file for rssh
OVERVIEW
rssh.conf is the configuration file for rssh. It allows the system administrator to control the behavior of the shell. Configuration key-
words are either used by themselves on a line, or followed by an equal sign ('=') and a configuration value. Comments start with a hash
('#') and can occur anywhere on the line. Configuration options are case insensitive. Spaces at the beginning or end of line, or between
the equal sign and the configuration keywords or values are ignored. If the value of a configuration option contains spaces, it (or at
least the space) must be enclosed in either single or double quotes.
A default configuration file is provided with the source distribution of rssh. If the configuration file is missing or contains errors,
ssh will lock out all users. If a config file is present, the default is to lock out users if no services have been explicitly allowed.
New in v2.1 is the ability to configure options on a per-user basis, using the user keyword. More details are below.
CONFIGURATION KEYWORDS
allowscp
Tells the shell that scp is allowed.
allowsftp
Tells the shell that sftp is allowed.
allowcvs
Tells the shell that cvs is allowed.
allowrdist
Tells the shell that rdist is allowed.
allowrsync
Tells the shell that rsync is allowed.
allowsvnserve
Tells the shell that svnserve is allowed.
umask
Sets the umask value for file creations in the scp/sftp session. This is normally set at login time by the user's shell. In order
not to use the system default, rssh must set the umask.
logfacility
Allows the system administrator to control what syslog facility rssh logs to. The facilities are the same as those used by sys-
logd.conf(5), or the C macros for the facilities can be used instead. For example:
logfacility=user
logfacility=LOG_USER
are equivalent, and tell rssh to use the user facility for logging to syslog.
chrootpath
Causes rssh (actually a helper program) to call the chroot() system call, changing the root of the file system to whatever directory
is specified. Note that the value on the right hand side of the equal sign is the name of a directory, not a command. For example:
chrootpath=/usr/chroot
will change the root of the virtual file system to /usr/chroot, preventing the user from being able to access anything below
/usr/chroot in the file system, and making /usr/chroot appear to be the root directory. Care must be taken to set up a proper
chroot jail; see the file CHROOT in the rssh source distribution for hints about how to do this. See also the chroot(2) man page.
If the user's home directory (as specified in /etc/passwd) is underneath the path specified by this keyword, then the user will be
chdir'd into their home directory. If it is not, then they will be chdir'd to the root of the chroot jail.
In other words, if the jail is /chroot, and your user's home directory is /chroot/home/user, then once rssh_chroot_helper changes
the root of the system, it will cd into /home/user inside the jail. However, if your user's home directory is given as /home/user
in /etc/passwd, then even if that directory exists in the jail, the chroot helper will not try to cd there. The user's normal home
directory must live inside the jail for this to work.
user
The user keyword allows for the configuration of options on a per-user basis. THIS KEYWORD OVERRIDES ALL OTHER KEYWORDS FOR THE
SPECIFIED USER. That is, if you use a user keyword for user foo, then foo will use only the settings in that user line, and not any
of the settings set with the keywords above. The user keyword's argument consists of a group of fields separated by a colon (':'),
as shown below. The fields are, in order:
username
The username of the user for whom the entry provides options
umask
The umask for this user, in octal, just as it would be specified to the shell
access bits
Six binary digits, which indicate whether the user is allowed to use rsync, rdist, cvs, sftp, scp and svnserve, in that
order. One means the command is allowed, zero means it is not.
path
The directory to which this user should be chrooted (this is not a command, it is a directory name). See chroot_path above
for complete details.
For example, you might have something like this:
user = luser:022:000010:
This does the following: for the user with the username "luser", set the umask to 022, disallow sftp, and allow scp. Because there
is no chroot path specified, the user will not be chrooted, regardless of default options set with the keywords above. If you
wanted this user to be chrooted, you would need to specify the chroot path explicitly, even if it should be the same as that set
using the chrootpath keyword. Remember that if there are spaces in the path, you need to quote it, something like this:
user = "luser:022:000010:/usr/local/chroot dir"
See the default rssh.conf file for more examples.
SEE ALSO
rssh(1), sshd(8), ssh(1), scp(1), sftp(1), svnserve(8), syslogd.conf(5), chroot(2).
man pages 7 Jul 2003 RSSH.CONF(5)
