Sponsored Content
Full Discussion: rlogin & telnet
Top Forums UNIX for Dummies Questions & Answers rlogin & telnet Post 9983 by dabrock on Tuesday 6th of November 2001 08:57:50 AM
Old 11-06-2001
As mentioned it was not the most secure decision. Perhaps I should metion that these were completely secured boxes and on an internal, network that was not accessable from outside. Also, even if someone had physically been able to gain access the contents of the machines were actually trivial enough not to worry us if someone did hack in.

I offer host.equiv only as a point of information, it is definitely too insecure to use on an exposed box. However, I want to clearify something: you only have the account equivalency that you transfer between machines, thus, <b>root</b> = <b>root</b>, but <b>ONLY root</b> = <b>root</b> so saying that you have root equivilancy is not exactly accurate. If you log in on a remote trusted machine as <b>user1</b> you can only be <b>user1</b> on the local machine so this method is not much more insure than using .rhost, except you don't have control of the exact accounts that are equivilent. In fact, it is very similar to trust between domains in a Windows network (host.equiv basically spells out a one-way trust in Windows terminology).

As for spoofing that is certainly a risk for any system and you should always have any server behind a properly setup firewall to avoid spoofing. If someone can hack through your firewall SSH can offer more protection. Again, the best solution is always the secure one such as SSH2.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

rsh & rlogin

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

telnet on AT&T MLS V

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

telnet, rlogin, ssh login probblem

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

telnet & su in shell script

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

diable telnet & ftp

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

rlogin, telnet connections timeout

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

rlogin,telnet-different or same?

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

script for nested rlogin and telnet

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

rlogin and telnet

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

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
HOSTS.EQUIV(5)						     Linux Programmer's Manual						    HOSTS.EQUIV(5)

NAME
hosts.equiv - list of hosts and users that are granted "trusted" r command access to your system DESCRIPTION
The file /etc/hosts.equiv 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|+@netgroup|-@netgroup [+|[-]username|+@netgroup|-@netgroup] 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 additional credentials, including possibly a password. For security reasons you should always use the FQDN of the hostname 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 honor the contents of this file only 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 considered a wildcard character which means "any host" only when the word promiscuous is added to the auth component line in your PAM file for the particular service (e.g., rlogin). EXAMPLE
Below are some example /etc/host.equiv or ~/.rhosts files. Allow any user to log in from any host: + Allow any user from host with a matching local account to log in: host Note: the use of +host is never a valid syntax, including attempting to specify that any user from the host is allowed. Allow any user from host to log in: host + Note: this is distinct from the previous example since it does not require a matching local account. Allow user from host to log in as any non-root user: host user Allow all users with matching local accounts from host to log in except for baduser: host -baduser host Deny all users from host: -host Note: the use of -host -user is never a valid syntax, including attempting to specify that a particular user from the host is not trusted. Allow all users with matching local accounts on all hosts in a netgroup: +@netgroup Disallow all users on all hosts in a netgroup: -@netgroup Allow all users in a netgroup to log in from host as any non-root user: host +@netgroup Allow all users with matching local accounts on all hosts in a netgroup except baduser: +@netgroup -baduser +@netgroup Note: the deny statements must always precede the allow statements because the file is processed sequentially until the first matching rule is found. SEE ALSO
rhosts(5), rlogind(8), rshd(8) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2015-07-23 HOSTS.EQUIV(5)
All times are GMT -4. The time now is 10:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy