04-24-2012
+ + in .rhosts is causing a "Permission Denied"
I have a user who has "+ +" at the top of his .rhosts file. He cannot "rsh NODE date" to a different box ( both are RHEL 5.4 ). If I remove the "+ +" then the "RSH" works. I have correct settings of node names/user in the .rhosts file.
I even tried adding to the second box's /etc/host.equiv:
-@untrusted_rsh
+@trusted_rsh
Why would the "+ +" cause a "Permission Denied" error?
Thanks in advance,
Joe Griffin
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi all,
i've got problem in running a script in background... i have written a script, and i want to run it everytime i log in, but when i log off i want the script to stay (i watch not to run two scripts at one time in the script).
so as a normal user i want to do:
$ screen my_script &
... (6 Replies)
Discussion started by: miechu
6 Replies
2. UNIX for Advanced & Expert Users
Hi,
When I try to run a script with ". "(dot space) in my home, it gives me error ".: Permission denied".
Any explanation for this behaviour?
Thanks in advance,
-Ashish (3 Replies)
Discussion started by: shriashishpatil
3 Replies
3. UNIX for Dummies Questions & Answers
HI All,
I am using solaris
i created a user adam and updated his permissions
in vi sudoers file as follows
adam ALL=(ALL) NOPASSWORD: ALL
...........
when i create user by logging as sudo user .
$ sudo useradd -d /home/kalyan -m -s /bin/sh kalyan
sudo: not found
... (6 Replies)
Discussion started by: kalyankalyan
6 Replies
4. UNIX for Advanced & Expert Users
guest@ulidtko:~$ id
uid=126(guest) gid=134(guest) groups=134(guest)
guest@ulidtko:~$ ls -ld /home
drwxr-xr-x 8 root root 4096 May 12 19:47 /home
guest@ulidtko:~$ ls -l /home
ls: cannot open directory /home: Permission denied
guest@ulidtko:~$ cat /proc/mounts
rootfs / rootfs rw 0 0... (4 Replies)
Discussion started by: ulidtko
4 Replies
5. OS X (Apple)
Hi,
I have two machines 1. MacOSx (Users --> userMac , IP - a.b.c.d)
2. FreeBSD (Users --> userBSD, IP- p.q.r.s)
I want to modify some files of FreeBSD on my MacOS. So, I mounted the FreeBSD folder on my Mac as follows.
$ sudo mount -o -P p.q.r.s:/usr/home/user... (5 Replies)
Discussion started by: akash.mahakode
5 Replies
6. Solaris
Let me preface with I am semi-new to Solaris. I work with it in the labs at work and that's about my extent (although I run Linux at home).
Well, a week ago security comes around with updated requirements, some of which are the need to audit all failures. For the life of me I cannot get a... (0 Replies)
Discussion started by: mph275
0 Replies
7. Linux
Hello friends,
I have scratched my system and after that when I am trying to access the console via root login it's failing with an error message of "permission denied". I am able to access the other login, I am having only problem with root and some other user login. I am using an telnet... (2 Replies)
Discussion started by: sanoop
2 Replies
8. UNIX for Advanced & Expert Users
Hello friends,
I have scratched my system and after that when I am trying to access the console via root login it's failing with an error message of "permission denied". I am able to access the other login, I am having only problem with root and some other user login. I am using an telnet... (7 Replies)
Discussion started by: sanoop
7 Replies
9. Solaris
hello everyone,
I am new on unix systems. I am working with a Solaris 10 OS.
When i try to change netmask on certain interface:
I get:
How can i enable permission for changing that ? I have administrator privileges.
Your help is much appreciated.
thanks, (13 Replies)
Discussion started by: pablod76
13 Replies
10. OS X (Apple)
Hi,
I hope this is the correct section in the forum to post as I'm trying to SSH from my MacBook.
I was looking to see whether ssh on my jailbroken iPhone 6s (10.3.1) still works fine and was following this old reddit guide. I installed OpenSSH&OpenSSL from Cydia and changed the password using... (7 Replies)
Discussion started by: hss1
7 Replies
LEARN ABOUT OSF1
hosts.equiv
hosts.equiv(4) Kernel Interfaces Manual hosts.equiv(4)
NAME
hosts.equiv - A file containing the names of remote systems and users that can execute commands on the local system
SYNOPSIS
/etc/hosts.equiv
DESCRIPTION
The /etc/hosts.equiv file and the .rhosts file in a user's home directory contain the names of remote hosts and users that are equivalent
to the local host or user. An equivalent host or user is allowed to access a local nonsuperuser account with the rsh command or rcp com-
mand, or to log in to such an account without having to supply a password.
The /etc/hosts.equiv file specifies equivalence for an entire system, while a user's .rhosts file specifies equivalence between that user
and remote users. The local user and the target system exist in the same area as the hosts.equiv file. The .rhosts file must be owned by
the user in whose home directory the file is located, or by the superuser. It cannot be a symbolic link.
Each line, or entry, in hosts.equiv or .rhosts may consist of the following: A blank line. A comment (begins with a #). A host name (a
string of any printable characters except newline, #, or white space). In addition, an NIS netgroup can be specified in place of the host
name. A host name followed by white space and a user name. In addition, an NIS netgroup can be specified in place of the host name, user
name, or both. A single plus (+) character. This means any host and user. The keyword NO_PLUS. This keyword disallows the use of the plus
character (+) to match any host or user on a system-wide basis. By default, the line containing this keyword is a comment. Remove the com-
ment character to disallow the use of the plus character.
Entries in the hosts.equiv file are either positive or negative. Positive entries allow access; negative entries deny access. The following
entries are positive: host name user name +@netgroup
In addition, the plus sign (+) can be used in place of the host name or user name. In place of the host name, it means any remote host. In
place of the user name, it means any user.
The following entries are negative: -host name -user name -@netgroup
To be allowed access or denied access, a user's remote host name and user name must match an entry in hosts.equiv or .rhosts. The
hosts.equiv file is searched first; if a match is found, the search ends. Therefore, the order in which the positive and negative entries
appear is important. If a match is not found, .rhosts is searched if it exists in the user's home directory.
A host name or user name can match an entry in hosts.equiv in one of the following ways: The official host name (not an alias) of the
remote host matches a host name in hosts.equiv. The remote user name matches a user name in hosts.equiv. If a user name parameter is
included in the hosts.equiv file, this means that the remote user is a trusted user and is allowed to rlogin to any local user account
without being prompted for a password. Otherwise, if the user name parameter is not specified in the hosts.equiv file, the name of the
remote user must match that of the local user. If the remote user name does not match a user name in hosts.equiv, the remote user name
matches the local user name.
CAUTIONS
For security purposes, the files /etc/hosts.equiv and .rhosts should exist and be readable and writable only by the owner, even if they are
empty.
EXAMPLES
The following are sample entries in an /etc/hosts.equiv file: # Allows access to users on host1 and host2 that have accounts on this host:
host1 host2 # Allows access to user johnson on host1 to any local user: host1 johnson # Allows access to all users on systems specified in
netgroup chicago +@chicago # Denies access to users specified in netgroup finance on host5 host5 -@finance # Allows access to all users on
all systems except root + -root
RELATED INFORMATION
Commands: rcp(1), rlogin(1), rsh(1)
Functions: ruserok(3).
Files: netgroup(4)
Daemons: rlogind(8), rshd(8) delim off
hosts.equiv(4)