08-25-2008
Quote:
Originally Posted by
seanovision
#!/bin/bash
for i in `cat nc.host`
do
nc -v $i
done
If you read carefully
man nc you will see the difference between
-v and
-z .
![Wink Smilie](https://www.unix.com/images/smilies/wink.gif)
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
hey guys, i am on a box named pluto and i need to be able to log into another box named genesis. i need to be able to ssh into genesis as root and not get asked for the password. what file do i need to edit on genesis to make this happen? i searched for the .rhosts file it doesn't seem to exist.... (1 Reply)
Discussion started by: Terrible
1 Replies
2. Shell Programming and Scripting
Hi,
My scripting skills are somewhat basic...
I need a way to log into a list of hostname/IPs as a user, su to root and then create/append root's .bashrc
Thanks (0 Replies)
Discussion started by: jag7720
0 Replies
3. IP Networking
From my machine (ubuntu), I can do
$ nc somemachine 80
But, when I want to connect to other machine that runs nc on different ports, it throws "Connection refused" error.
The same error occurs on my local machine. For example,
nc -l 5555
nc x.x.x.x 5555 --> this throws "Connection... (2 Replies)
Discussion started by: dinga
2 Replies
4. Shell Programming and Scripting
SERVICE NOTIFICATION: SOC;invoice-skysmart-01.net;monthly_process_check;CRITICAL;notify-by-email;CRITICAL: (0) instance(s) of (monthly-processor6) running on host (less than 1)
SERVICE NOTIFICATION: SOC;invoice-02.skysmart.net;JAVA_PROCESS_CHECK;CRITICAL;notify-by-email;CRITICAL: (0) instance(s)... (6 Replies)
Discussion started by: SkySmart
6 Replies
5. Shell Programming and Scripting
i want to change user to "root" from another user while running a script. how can i automatically feed the password? for example, i want to write a script say "script.sh"... it will first run the command "p" as mhmn user, and then it will change the user to "root" by using "su - root" command. at... (1 Reply)
Discussion started by: mhmn
1 Replies
6. Shell Programming and Scripting
Hi friends,
i need to prepare a script ( in perl)
i have a file called "demo.exe" in my local unix host.
i have a list of remote hosts in a file "hosts.txt"
now i need to push "demo.exe" file to all the hosts in "hosts.txt" file.
for this i need to prepare a script(in perl, but shell... (5 Replies)
Discussion started by: siva kumar
5 Replies
7. UNIX for Dummies Questions & Answers
Hi:
How to list processes from all hosts, as opposed to the one you are working at?
"ps ux" appears to list processes of the user on a single host only.
Thanks.
N.B Phil (5 Replies)
Discussion started by: phil518
5 Replies
8. Shell Programming and Scripting
Hi All,
Need to run the netstat -i command on the list of hosts and check if "Ierrs" and "Oerrs" has value greaterthan 0.
for Ex: below output, driver bge1 and bge3 has Oerrs and Ierrs value > 0, So, script should report saying
"Netstat status for $host, driver bge1 has Oerrs = 20, Failed"... (5 Replies)
Discussion started by: Optimus81
5 Replies
9. Cybersecurity
Hello,
with the following problem I feel helpless because I do not know where to look for the problem.
Sorry in advance for my poor English.
At some point the interaction with people on Freenode IRC has become mysterious and offending so that I checked my modem/router device. When I tried to... (2 Replies)
Discussion started by: SInt
2 Replies
10. Solaris
Am trying to copy a tar file onto a series of remote hosts and untar it at the destination. Need to do this without having to do multiple ssh.
Actions to perform within a single ssh session via shell script
- copy a file
- untar at destination (remote host)
OS : Linux RHEL6 (3 Replies)
Discussion started by: sankasu
3 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