| 1 |
<pre>Network Working Group A. McKenzie |
| 2 |
RFC #521 BBN-NET |
| 3 |
NIC #16855 30 May 1973 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">Restricted Use of IMP DDT</span> |
| 7 |
|
| 8 |
|
| 9 |
At the recent workshop on "Automated Resource Sharing on the |
| 10 |
ARPANET", considerable interest was expressed on the topic of network |
| 11 |
security. In particular, representatives of several sites felt that |
| 12 |
uncontrolled use of IMP DDT made access control mechanisms quite |
| 13 |
vulnerable to interception or tampering.* Individuals at the workshop |
| 14 |
seemed to be in general agreement that use of DDT should be much more |
| 15 |
controlled than at present. In addition, as the network continues to |
| 16 |
take on a more and more operational character, and NCC use of DDT (which |
| 17 |
must be coordinated with other DDT usage) increases** we begin to see |
| 18 |
other reasons for controlling access to the DDT mechanism. |
| 19 |
|
| 20 |
Currently, and for the foreseeable future, it is important that the |
| 21 |
NCC be able to use DDT at any IMP at any time. It is also sometimes |
| 22 |
necessary for site personnel to be able to operate a stand alone DDT |
| 23 |
after an IMP crash. Sometimes the NCC needs to ask site personnel to |
| 24 |
operate the IMP DDT for the NCC if the network is partitioned. We have |
| 25 |
protected all DDT commands that can affect the running IMP program by |
| 26 |
requiring that sense switch 4 be turned on at the site, or a software |
| 27 |
override flag be enabled. Only the BBN IMP Teletype, the BBN TIP |
| 28 |
Teletype, and the PDP-1 can enable override. The NCC monitors these |
| 29 |
flags and reports any change in status. |
| 30 |
|
| 31 |
In line with this approach, we will soon modify the IMP system so |
| 32 |
that any access to IMP DDT will require the same enabling actions (sense |
| 33 |
switch four turned on or override enabled from BBN) now required for |
| 34 |
core modification. This will still allow the NCC the same ability to |
| 35 |
operate DDT which it now has, and will permit site personnel to operate |
| 36 |
DDT at the request of the NCC. As is currently true, the NCC will |
| 37 |
|
| 38 |
|
| 39 |
---------------- |
| 40 |
*Examples are easy to construct, but are intentionally omitted from this |
| 41 |
document. |
| 42 |
|
| 43 |
**DDT is currently used by the NCC operators for core verification, for |
| 44 |
interface debugging, for loading TIP and VDH code, etc. There is |
| 45 |
discussion of using DDT in conjunction with an "auto-dialer" to examine |
| 46 |
a TIP's "view" of a modem port at the same time that the auto-dialer is |
| 47 |
examining the outside world's "view" of the port, of running "automatic" |
| 48 |
core verification, of loading Satellite IMP code, etc. |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">McKenzie [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc521">RFC 521</a> Restricted Use of IMP DDT May 1973</span> |
| 55 |
|
| 56 |
|
| 57 |
monitor the setting of sense switch four and take appropriate action if |
| 58 |
unauthorized use is observed. We feel that this change will be |
| 59 |
sufficient to discourage "hackers", although it is obviously |
| 60 |
insufficient to protect a node against a determined and malicious |
| 61 |
attack. |
| 62 |
|
| 63 |
It should be noted that it is not our current intent to prohibit |
| 64 |
occasional use of DDT for communication between sites via "DDT" |
| 65 |
messages. Currently, there are two DDT commands, C and L, which set the |
| 66 |
single-character message and multi-character message headers |
| 67 |
respectively. We will continue this facility, either by always |
| 68 |
permitting the use of these DDT commands, or by implementing some new |
| 69 |
code outside DDT for this purpose. |
| 70 |
|
| 71 |
|
| 72 |
|
| 73 |
|
| 74 |
|
| 75 |
|
| 76 |
|
| 77 |
|
| 78 |
|
| 79 |
|
| 80 |
[ This RFC was put into machine readable form for entry ] |
| 81 |
[ into the online RFC archives by Alex McKenzie with ] |
| 82 |
[ support from GTE, formerly BBN Corp. 10/99 ] |
| 83 |
|
| 84 |
|
| 85 |
|
| 86 |
|
| 87 |
|
| 88 |
|
| 89 |
|
| 90 |
|
| 91 |
|
| 92 |
|
| 93 |
|
| 94 |
|
| 95 |
|
| 96 |
|
| 97 |
|
| 98 |
|
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
McKenzie [Page 2] |
| 109 |
</pre> |