10-24-2001
Anent,
Sorry I was wrong in saying that with rlogin you don't need to enter a username/password.
You may need to specify a username if:
1 you want to use a different username to your current username 2 you are using a rlogin client program in windows
However you may or may not be required to specify a login password depending on if the ~/.rhosts file in the remote machine you want to login into is configure correctly.
Thanks for correcting me, I should have said that ~/.rhosts needs to be configured to allow password less logins.
Andy
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm trying to execute the next command:
" rsh CompName date "
which means i want to get the date from a machine which i have its CompName.
but i get the answer : "Connection refused"
what do i need to do ?
how can i sign myself as user or guest in the other machine ?
thanks in... (2 Replies)
Discussion started by: Inbal
2 Replies
2. Cybersecurity
How do I enable telnet access to a system running AT&T MLS? (1 Reply)
Discussion started by: smartgod
1 Replies
3. UNIX for Dummies Questions & Answers
Hello Friends,
I had an IRIX box won't let me login with any IDs (even root) Telnet, Rlogin, SSh. However, I can login by single user with root ID.
Telnet login >>> Connection closed by forgeign host.
Rlogin >>> Connection closed
SSh login >>> connection to address ???.????.???.??? ... (1 Reply)
Discussion started by: anphdula
1 Replies
4. Shell Programming and Scripting
Hi,
Any scripting experts out there that can point me to the right direction of writing a script using telnet and su to access a server without any users interaction such as login and entering passwd. Thanks.
Thanks in advance
vastare (1 Reply)
Discussion started by: vastare
1 Replies
5. UNIX for Advanced & Expert Users
Hi All,
I need to stop all the services for telnet & FTP as we want our
server to be more secure.
Please give me some steps for jumping to SSH protocol.
How can i disable telnet & ftp service on my server. (1 Reply)
Discussion started by: pradeep_desh
1 Replies
6. Solaris
Hi,
I have a Sun Ultra 5 desktop with Solaris 8. When I telnet/rlogin into any other host, the connection closes after few hours of inactivity.
I also have another Windows box which I use rarely. But when I telnet/rlogin into the same hosts using putty, the connection stays for days without any... (5 Replies)
Discussion started by: dr_gsb
5 Replies
7. IP Networking
Hai guys,
Both "rlogin" and "telnet" are used to login remote host.Is there any differece between these 2 commands? (or) are both same?
Thanks (1 Reply)
Discussion started by: Felicia23
1 Replies
8. Shell Programming and Scripting
I want to write a script that rlogins to a couple machines and then from the last machine, telnet into a final machine and execute a command. So in pseudocode it would look like:
rlogin host1
from host1 rlogin host2
from host2 telnet host3
from host 3 execute command
The reason for the... (6 Replies)
Discussion started by: mcburke38
6 Replies
9. Shell Programming and Scripting
I want to make a script which will execute a command from a remote server like below
rlogin server1
then
telnet server2
(username, password will be given)
now execute command (it may "ls -l *.txt") and give the output
I've to do this manually but want to make it automatic
Script may... (4 Replies)
Discussion started by: shoeb
4 Replies
10. Shell Programming and Scripting
cat & telnet
hello,
I need some help on using a file with the cat command. I want to set up a telnet connection with a network device with the ip-adress 10.3.0.1. Just executing the command 'telnet 10.3.0.1' gives a menu. For example, to show the help of the menu, you... (2 Replies)
Discussion started by: michealvh
2 Replies
LEARN ABOUT OSX
hosts.equiv
HOSTS.EQUIV(5) BSD File Formats Manual HOSTS.EQUIV(5)
NAME
hosts.equiv, .rhosts -- trusted remote hosts and host-user pairs
DESCRIPTION
The hosts.equiv and .rhosts files list hosts and users which are ``trusted'' by the local host when a connection is made via rlogind(8),
rshd(8), or any other server that uses ruserok(3). This mechanism bypasses password checks, and is required for access via rsh(1).
Each line of these files has the format:
hostname [username]
The hostname may be specified as a host name (typically a fully qualified host name in a DNS environment) or address, +@netgroup (from which
only the host names are checked), or a ``+'' wildcard (allow all hosts).
The username, if specified, may be given as a user name on the remote host, +@netgroup (from which only the user names are checked), or a
``+'' wildcard (allow all remote users).
If a username is specified, only that user from the specified host may login to the local machine. If a username is not specified, any user
may login with the same user name.
EXAMPLES
somehost
A common usage: users on somehost may login to the local host as the same user name.
somehost username
The user username on somehost may login to the local host. If specified in /etc/hosts.equiv, the user may login with only the same
user name.
+@anetgroup username
The user username may login to the local host from any machine listed in the netgroup anetgroup.
+
+ +
Two severe security hazards. In the first case, allows a user on any machine to login to the local host as the same user name. In the
second case, allows any user on any machine to login to the local host (as any user, if in /etc/hosts.equiv).
WARNINGS
The username checks provided by this mechanism are not secure, as the remote user name is received by the server unchecked for validity.
Therefore this mechanism should only be used in an environment where all hosts are completely trusted.
A numeric host address instead of a host name can help security considerations somewhat; the address is then used directly by iruserok(3).
When a username (or netgroup, or +) is specified in /etc/hosts.equiv, that user (or group of users, or all users, respectively) may login to
the local host as any local user. Usernames in /etc/hosts.equiv should therefore be used with extreme caution, or not at all.
A .rhosts file must be owned by the user whose home directory it resides in, and must be writable only by that user.
Logins as root only check root's .rhosts file; the /etc/hosts.equiv file is not checked for security. Access permitted through root's
.rhosts file is typically only for rsh(1), as root must still login on the console for an interactive login such as rlogin(1).
FILES
/etc/hosts.equiv Global trusted host-user pairs list
~/.rhosts Per-user trusted host-user pairs list
SEE ALSO
rcp(1), rlogin(1), rsh(1), rcmd(3), ruserok(3), netgroup(5)
HISTORY
The .rhosts file format appeared in 4.2BSD.
BUGS
The ruserok(3) implementation currently skips negative entries (preceded with a ``-'' sign) and does not treat them as ``short-circuit'' neg-
ative entries.
BSD
November 26, 1997 BSD