🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: mod.protocols.tcp-ip
2 messages
2 total messages Started by PERRY Mon, 06 Apr 1987 12:19
Re: My Broadcast
#1597
Author: PERRY
Date: Mon, 06 Apr 1987 12:19
21 lines
1597 bytes
Jordan, you are right in your assumptions that people will get annoyed
that what happened was allowed to happen.

By the way, I am the program manager of the Arpanet in the Information
Science and Technology Office of DARPA, located in Roslin (Arlington), not
the Pentagon.

I would like suggestions as to what you, or anyone else, think should be
done to prevent such occurances in the furture.  There are many drastic
choices one could make.  Is there a reasonable one?  Perhaps some one
from Sun could volunteer what there action will be in light of this
revelation.  I certainly hope that the community can come up with a good
solution, because I know that when the problem gets solved from the top
the solutions will reflect their concerns.

Think about this situation and I think you will all agree that this is
 a serious problem that could cripple the Arpanet and anyother net that
lets things like this happen without control.

dennis
-------
My Broadcast
#1586
Author: bzs
Date: Mon, 06 Apr 1987 19:29
31 lines
1699 bytes
From Dennis Perry:
>I would like suggestions as to what you, or anyone else, think should be
>done to prevent such occurances in the furture.

Solution:

Edit /etc/servers and remove the rwalld line. This will disable the
remote service. The local "write to all users" program, 'wall', can
still be used on any individual system. To shout to all systems in an
area either have the operators log in and run wall locally or execute
it via 'rsh system wall ..msg..' from a locally trusted site (as per
the rsh restrictions.) A command file could be created trivially which
simulated "rwall" to a selected set of sites:

#!/bin/sh
echo "Enter message to be sent to all systems (one line)"
echo -n 'MESSAGE: '
read msg
for i in host1 host2 etc...
do
	rsh $i wall $msg
done

(I didn't test this, but I think the point is clear.)

This can be further enhanced by removing the rwall binary from your
systems, but if you don't support the daemon, you're not going to see
any broadcasts, so it's under your control. Done.

	-Barry Shein, Boston University
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads