04-08-2008
If by "trusted" you mean you have hosts.deny or firewall rules or something, then you still need to tell us more about those.
Now that you have it in /etc/hosts and have checked that you can ping by name (you have, yes?) it's probably better to put in the host name from /etc/hosts
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi.
i was wondering if anyone can show me or direct me on setting up a ntp server under redhat.. Is there any howtos so i can get familar to it "any good sites" (3 Replies)
Discussion started by: souldier
3 Replies
2. Linux
RH 7.2
I have 2 unrelated questions -
1.) I have been able to configure and run ntp but cannot figure out how to start the service upon reboot. I have read the man pages for ntsysv - this is a manual action, but I want to drop a tarball of config files on a new installation and cannot... (1 Reply)
Discussion started by: jalburger
1 Replies
3. Solaris
All,
How do you set a Solaris 9 server which received ntp updates from a ntp server to broadcast them on a local subnet. I have created a /etc/inet/ntp.conf file to receive the updates from a server on network and need to make this server become like a ntp relay from the main server.
Any... (1 Reply)
Discussion started by: bubba112557
1 Replies
4. IP Networking
Hello Guys,
i have a problem my local server is not getting synchronized with ntpd server.
1)ntpq -p is giving the following output
remote refid st t when poll reach delay offset jitter
==============================================================================
... (9 Replies)
Discussion started by: mannam srinivas
9 Replies
5. Red Hat
Hi All....
I need to configure NTP server in my network, which is heterogeneous, containing Linux as well as windows systems. I'm planning to configure it on RHEL 5.0. What are the prerequisites for this and do I need to register this server?
Can anyone give me as many information as... (1 Reply)
Discussion started by: Amol21
1 Replies
6. Linux
All here, thank you for listening. Now I've set up a Linux NTP server by adding a external windows NTP server in /etc/ntp.conf. Then I start the ntpd daemon. But how often does the Linux NTP server update its time with the external NTP server? I've looked up everywhere but found no information... (1 Reply)
Discussion started by: MichaelLi
1 Replies
7. Linux
Hi folks, I have developed a Linux server for my customer. After migrating the server to my customer site, I was trying to sync its time to the NTP time servers at my customer site.
Below is the ntp.conf:
% vi /etc/ntp.conf
# Permit time synchronization with our time source, but do not
# permit... (2 Replies)
Discussion started by: kimurayuki
2 Replies
8. HP-UX
Hi
I wonder if its possible to setup NTP clients running HP-UX o.s. from a solaris 10 NTP server?
FR (3 Replies)
Discussion started by: fretagi
3 Replies
9. Red Hat
Hi,
I have two ntp servers in my cluster and I want all the nodes in my cluster to sync with either of the ntp servers or just one. Unfortunately it keep rotating the sync, between my ntp server 1, ntp server 2 and local. Is there anyway I can change the sync to avoid local?
# ntpq -p
... (3 Replies)
Discussion started by: pjeedu2247
3 Replies
10. Linux
Hello
I need to create NTP server for all my devices, What is the best OS for NTP Server? "CentOS, Redhat, Ubuntu "
I tried before Ubuntu but some of device not detect the server
Need your recommendation
Thank you (2 Replies)
Discussion started by: moudmm
2 Replies
LEARN ABOUT MOJAVE
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