Free rsh software for linux

mrsh project runs a remote command on multiple hosts. Rather than repeat an rsh command across a set of hosts, a single mrsh command can do the job.

For instance, you can use it to do things like:

mrsh sleepy dopey stoner -- df /var/log

SYNTAX

mrsh [ -prst ] [ -P rsh_path ] host ... -- command ...

SlackCheck allows users to keep many Slackware machines up to date with the latest packages. All upgrades are performed from single machine though SSH (or RSH).
SlackCheck project generates an upgrade script and list of non-standard packages for every machine.
Enhancements:
- Update file generation was sped up by factor of 3.
- The --verbose option was added to see what packages will be upgraded.
- A bug was fixed that prevented the --gen command from working after --sync.

GNU Shishi project is a (still incomplete) implementation of Kerberos 5, which can be used to authenticate users in distributed systems. GNU Shishi contains a library that can be used by application developers, and a command line utility for users.

Shishi supports Kerberos authenticated telnet client/server, IMAP client/server (via GSSAPI), SSH client/server (via GSSAPI), rsh/rlogin client, and a PAM module for host security.

NATting SOHO firewall is a firewall script for iptables.

# Model NATting SOHO firewall for SP article
# by Jay Beale (jay@bastille-linux.org)
#
# Warning: youre going to have to hack this for your own purposes.
#

# Assumptions:
# your internal network is 192.168.1.0/24 on eth1
# your internet IP is 10.0.0.1 on eth0
# your internal network IP on eth1 is 192.168.1.1
#
# Additonally:
# you have another internal network, a DMZ: 192.168.2.0/24 on eth2

$INTERNAL_IP = 192.168.1.1
$INTERNAL_NET = 192.168.1.0/24

$INTERNET = 10.0.0.1

$DMZ = 192.168.2.0/24

# Insert the required kernel modules
modprobe iptable_nat
modprobe ip_conntrack
modprobe ip_conntrack_ftp

# Set default policies for packets going through this firewall box

iptables -t nat -P PREROUTING DROP
iptables -t nat -P POSTROUTING DROP
iptables -P FORWARD DROP

# Set default policies for packet entering this box

iptables -P OUTPUT ALLOW
iptables -P INPUT ALLOW

# Kill spoofed packets

for f in /proc/sys/net/ipv4/conf/*/rp_filter; do
echo 1 > $f
done

# Anything coming from our internal network should have only our addresses!
iptables -A FORWARD -i eth1 -s ! $INTERNAL_NET -j DROP

# Anything coming from the Internet should have a real Internet address
iptables -A FORWARD -i eth0 -s 192.168.0.0/16 -j DROP
iptables -A FORWARD -i eth0 -s 172.16.0.0/12 -j DROP
iptables -A FORWARD -i eth0 -s 10.0.0.0/8 -j DROP

# Note:There are more "reserved" networks, but these are the classical ones.

# Block outgoing network filesharing protocols that arent designed
# to leave the LAN

# SMB / Windows filesharing
iptables -A FORWARD -p tcp --sport 137:139 -j DROP
iptables -A FORWARD -p udp --sport 137:139 -j DROP
# NFS Mount Service (TCP/UDP 635)
iptables -A FORWARD -p tcp --sport 635 -j DROP
iptables -A FORWARD -p udp --sport 635 -j DROP
# NFS (TCP/UDP 2049)
iptables -A FORWARD -p tcp --sport 2049 -j DROP
iptables -A FORWARD -p udp --sport 2049 -j DROP
# Portmapper (TCP/UDP 111)
iptables -A FORWARD -p tcp --sport 111 -j DROP
iptables -A FORWARD -p udp --sport 111 -j DROP

# Block incoming syslog, lpr, rsh, rexec...
iptables -A FORWARD -i eth0 -p udp --dport syslog -j DROP
iptables -A FORWARD -i eth0 -p tcp --dport 515 -j DROP
iptables -A FORWARD -i eth0 -p tcp --dport 514 -j DROP
iptables -A FORWARD -i eth0 -p tcp --dport 512 -j DROP

###
# Transparently proxy all web-surfing through Squid box

$SQUID = 192.168.1.2:8080
$SQUIDSSL = 192.168.1.2:443
iptables -t nat -A PREROUTING -i eth1 -tcp --dport 80 -j DNAT --to $SQUID
iptables -t nat -A PREROUTING -i eth1 -tcp --dport 443 -j DNAT --to $SQUIDSSL

# Transparently forward all outgoing mail to a relay host

$SMTP = 192.168.1.3
iptables -t nat -A PREROUTING -i eth1 -tcp --dport 25 -j DNAT --to $SMTP

# Transparently redirect web connections from outside to the DMZ web
# server

$DMZ_WEB = 192.168.2.2
iptables -t nat -A PREROUTING -i eth0 -d 192.168.1.1 -dport 80 -j DNAT --to $DMZ_WEB

# Source NAT to get Internet traffic through
iptables -t nat -A POSTROUTING -o eth1 -j SNAT --to $INTERNET


# Activate the forwarding!
echo 1 >/proc/sys/net/ipv4/ip_forward

Rconfig is intended to manage configuration files across heterogenous groups of machines. The configuration for each machine is determined by a set of rdist trees based on the various tags such as OS, hostname, and architecture.

Files in more specific rdist trees take priority. A basic setup would consist of a common directory, and then optionally one directory per machine in order to override any of the files in the common area.

Remote configuration requires passwordless root RSH/SSH from a host with direct access to the rconfig basedir. Target machines will require rdist but not rconfig installed.

distmake is a distributed make program.
distmake is a distributed, parallel, GNU make compatible make program.
distmake reads a Makefile, and distributes builds targets over a set of build servers on the network.
distmake is fully compatible with GNU make 3.80 on which is it based.
distmake should compile on any POSIX compliant platforms.
It has been reported to compile and work on :
Linux 2.4 on x86
Solaris 2.8 on sparc
Cygwin
How distmake works:
Before the make process is started, distmake starts a ONC RPC server (rpc.bldserver) on all build servers with a rsh command (but see below how to change this and use ssh instead). This RPC server listens for distmake requests, processes jobs (builds) and reports execution status. When all jobs are done, distmake kills each RPC server on remote machines.
Controlling distmake:
The following environment variables are used by distmake:
DISTMAKE_RSH, if present, should point to a rsh compatible program (ssh is a good candidate if security is a concern for your site).
DISTMAKE_RPCBLDSERVER, if present, should point to the rpc.bldserver program, built with distmake. If this variable does not exist, a compile-time value is used instead. (PREFIX/bin/rpc.bldserver).
Debugging distmake:
Use distmake --debug=r[,other debug flags]
Enhancements:
- This release offers two modes of operation: automatic on-demand start of remote build servers, or use waiting daemons.
- This combines the behaviours of releases 0.2 and 0.3.1.

Socketpipe project connects over a TCP/IP socket a remote command specified to a local input generation command and/or a local output processing command.
The input and output of the remote command are appropriately redirected so that the remote commands input will come from the local input generation command and the remote commands output will be sent to the local output processing command.
The remote command is executed on the machine accessed through the login command. The socketpipe executable should be available through the execution path in the remote machine.
The braces used for delimiting the commands and their arguments should be space-separated and can be nested. This feature allows you to setup complex and efficient topologies of distributed communicating processes.
Although the initial socketpipe communication setup is performed through client-server intermediaries such as ssh(1) or rsh(1), the communication channel that socketpipe establishes is a direct socket connection between the local and the remote commands.
Without the use of socketpipe, when piping remote data through ssh(1) or rsh(1), each data block is read at the local end by the respective client, is sent to the remote daemon and written out again to the remote process.
The use of socketpipe removes the inefficiency of the multiple data copies and context switches and can in some cases provide dramatic throughput improvements. On the other hand, the confidentiality and integrity of the data passing through socketpipes data channel is not protected; socketpipe should therefore be used only within a confined LAN environment.
(The authentication process uses the protocol of the underlying login program and is no more or less vulnerable than using the program in isolation; ssh(1) remains secure, rsh(1) continues to be insecure.)
Enhancements:
- This version corrects a bug in the command parsing of the Windows version of socketpipe.

InetUtils is a collection of common network programs. The GNU whois client reads a whois-servers file to figure out which whois server to use. It wont always pick the best server; whois.internic.net seems to know something about nic.ddn.mil, but the GNU whois client will use nic.ddn.mil to look up nic.ddn.mil if you use the configuration file we supply. Our configuration file probably also does not have a complete list of whois servers; feel free to send information about additional whois servers to our developers.
There are probably many BSD dependencies remaining, but inetutils is believed
to work on the following system types (and others may work):
i486-gnu0.2
i486-pc-linux-gnu
m68k-hp-netbsd1.2
sparc-sun-netbsd1.2
sparc-sun-sunos4.1.4
sparc-sun-solaris2.5
The file `paths contains a list of all paths used by programs in this distribution, and rules to find values for them. To change a path PATH_FOO, you may either tell configure, by using `--with-path-foo=VALUE (where VALUE may contain references to make variables such as `$(bindir)), or edit the `paths file.
If you wish to build only the clients or only the servers, you may wish to use the --disable-servers or --disable-clients options when invoking `configure. You can also use --enable- or --disable- to control whether to build individual programs; if you explicitly specify whether to build a program, that will override the values specified by --disable-clients or --disable-servers.
Notes:
1) all the manpages will be installed, regardless of which programs are built. The whois server list will also be installed. You can use `make install-exec instead of `make install if you do not want to install these files.
2) All of the r* commands clients, rcp, rlogin, rsh, need to be install setuid root to work correctly they use priviledge ports for communication.
Some known deficiencies:
o Many programs do not support long options, such as --version or --help.
o The authentication and encryption options have not been tested.
Enhancements:
- configure.ac: Bump version to 1.4.2
- NEWS: Update for inetutils 1.4.2