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
RSH(1) BSD General Commands Manual RSH(1)
NAME
rsh -- remote shell
SYNOPSIS
rsh [-46dn] [-l username] [-p port] host [command]
rsh [-46dn] [-p port] username@host [command]
DESCRIPTION
rsh executes command on host.
rsh copies its standard input to the remote command, the standard output of the remote command to its standard output, and the standard error
of the remote command to its standard error. Interrupt, quit and terminate signals are propagated to the remote command; rsh normally termi-
nates when the remote command does. The options are as follows:
-4 Use IPv4 addresses only.
-6 Use IPv6 addresses only.
-d The -d option turns on socket debugging (using setsockopt(2)) on the TCP sockets used for communication with the remote host.
-l username By default, the remote username is the same as the local username. The -l option or the username@host format allow the remote
name to be specified.
-n The -n option redirects input from the special device /dev/null (see the BUGS section of this manual page).
-p port Uses the given port instead of the one assigned to the service ``shell''. May be given either as symbolic name or as number.
If no command is given, note that rlogin(1) is started, which may need a different daemon (rlogind(8) instead of rshd(8)) run-
ning on the server; you want to pass the rshd(8) port number in that case.
If no command is specified, you will be logged in on the remote host using rlogin(1).
Shell metacharacters which are not quoted are interpreted on local machine, while quoted metacharacters are interpreted on the remote
machine. For example, the command
rsh otherhost cat remotefile >> localfile
appends the remote file remotefile to the local file localfile, while
rsh otherhost cat remotefile ">>" other_remotefile
appends remotefile to other_remotefile.
FILES
/etc/hosts
SEE ALSO
rcmd(1), rlogin(1), rcmd(3), hosts.equiv(5), rhosts(5), environ(7)
HISTORY
The rsh command appeared in 4.2BSD.
BUGS
If you are using csh(1) and put a rsh in the background without redirecting its input away from the terminal, it will block even if no reads
are posted by the remote command. If no input is desired you should redirect the input of rsh to /dev/null using the -n option.
You cannot run an interactive command (like rogue(6) or vi(1)) using rsh; use rlogin(1) instead.
Stop signals stop the local rsh process only; this is arguably wrong, but currently hard to fix for reasons too complicated to explain here.
BSD
March 9, 2005 BSD