Sponsored Content
Full Discussion: become SU - ...Silently
Top Forums Shell Programming and Scripting become SU - ...Silently Post 302069507 by Klashxx on Monday 27th of March 2006 05:31:23 AM
Old 03-27-2006
Yes , u have to touch /etc/hosts as root

See de man pages of remsh and rlogin for more..

Cheers
 

2 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

execute a command silently or quietly within a shell

How do I suspend output of commands and tools that sometimes utter unwanted output? I know that I can always pipe to null or some such thing, but is there a simpler more elegant (i.e. accepted) practice? (4 Replies)
Discussion started by: lumix
4 Replies

2. Shell Programming and Scripting

Echoing silently?

I know, sounds mutually exclusive :-) I have a script where I ask for a password and store it in a variable, and then use it with sudo on an array of other hosts. The password winds up being choed back to my terminal as well as to the process on the remote host, like: Attempting to update... (2 Replies)
Discussion started by: jnojr
2 Replies
HOSTS.EQUIV(5)						     Linux Programmer's Manual						    HOSTS.EQUIV(5)

NAME
/etc/hosts.equiv - list of hosts and users that are granted "trusted" r command access to your system DESCRIPTION
The hosts.equiv file allows or denies hosts and users to use the r-commands (e.g., rlogin, rsh or rcp) without supplying a password. The file uses the following format: [ + | - ] [hostname] [username] The hostname is the name of a host which is logically equivalent to the local host. Users logged into that host are allowed to access like-named user accounts on the local host without supplying a password. The hostname may be (optionally) preceded by a plus (+) sign. If the plus sign is used alone it allows any host to access your system. You can explicitly deny access to a host by preceding the hostname by a minus (-) sign. Users from that host must always supply a password. For security reasons you should always use the FQDN of the host- name and not the short hostname. The username entry grants a specific user access to all user accounts (except root) without supplying a password. That means the user is NOT restricted to like-named accounts. The username may be (optionally) preceded by a plus (+) sign. You can also explicitly deny access to a specific user by preceding the username with a minus (-) sign. This says that the user is not trusted no matter what other entries for that host exist. Netgroups can be specified by preceding the netgroup by an @ sign. Be extremely careful when using the plus (+) sign. A simple typographical error could result in a standalone plus sign. A standalone plus sign is a wildcard character that means "any host"! FILES
/etc/hosts.equiv NOTES
Some systems will only honor the contents of this file when it has owner root and no write permission for anybody else. Some exceptionally paranoid systems even require that there be no other hard links to the file. Modern systems use the Pluggable Authentication Modules library (PAM). With PAM a standalone plus sign is only considered a wildcard char- acter which means "any host" when the word promiscuous is added to the auth component line in your PAM file for the particular service (e.g., rlogin). SEE ALSO
rhosts(5), rlogind(8), rshd(8) COLOPHON
This page is part of release 3.25 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 2003-08-24 HOSTS.EQUIV(5)
All times are GMT -4. The time now is 11:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy