| 1 |
<pre>Network Working Group F. da Cruz |
| 2 |
Request for Comments: 2839 J. Altman |
| 3 |
Category: Informational Columbia University |
| 4 |
May 2000 |
| 5 |
|
| 6 |
<span class="h1">Internet Kermit Service</span> |
| 7 |
|
| 8 |
Status of this Memo |
| 9 |
|
| 10 |
This memo provides information for the Internet community. It does |
| 11 |
not specify an Internet standard of any kind. Distribution of this |
| 12 |
memo is unlimited. |
| 13 |
|
| 14 |
Copyright Notice |
| 15 |
|
| 16 |
Copyright (C) The Internet Society (2000). All Rights Reserved. |
| 17 |
|
| 18 |
ABSTRACT |
| 19 |
|
| 20 |
This document describes a new file transfer service for the Internet |
| 21 |
based on Telnet Protocol for option negotiation and Kermit Protocol |
| 22 |
for file transfer and management. The Internet Kermit Service |
| 23 |
provides access to both authenticated and anonymous users. The use |
| 24 |
of Kermit protocol over a Telnet connection provides several |
| 25 |
advantages over FTP, including easy traversal of firewalls, transfers |
| 26 |
over multiple transports, and security via a combination of supported |
| 27 |
Telnet authentication and encryption option negotiations, plus |
| 28 |
significant functional benefits. While this document describes a new |
| 29 |
service for the Internet, the clients for this service already exist |
| 30 |
on most platforms in the form of Telnet clients that support the |
| 31 |
Kermit file transfer protocol. These clients are available not only |
| 32 |
from Columbia University's Kermit Project but also numerous third |
| 33 |
parties. |
| 34 |
|
| 35 |
TABLE OF CONTENTS |
| 36 |
|
| 37 |
<a href="#section-1">1</a>. INTRODUCTION ................................................ <a href="#page-2">2</a> |
| 38 |
<a href="#section-2">2</a>. BACKGROUND .................................................. <a href="#page-3">3</a> |
| 39 |
<a href="#section-2.1">2.1</a>. History ................................................... <a href="#page-3">3</a> |
| 40 |
<a href="#section-2.2">2.2</a>. Motivation ................................................ <a href="#page-4">4</a> |
| 41 |
<a href="#section-3">3</a>. THE INTERNET KERMIT SERVICE MODEL ........................... <a href="#page-7">7</a> |
| 42 |
<a href="#section-3.1">3.1</a>. Server-Side Kermit Server ................................. <a href="#page-7">7</a> |
| 43 |
<a href="#section-3.2">3.2</a>. Client-Side Kermit Server ................................. <a href="#page-8">8</a> |
| 44 |
<a href="#section-3.3">3.3</a>. Loosely Coupled Operation ................................. <a href="#page-9">9</a> |
| 45 |
<a href="#section-4">4</a>. SECURITY CONSIDERATIONS .....................................<a href="#page-10">10</a> |
| 46 |
<a href="#section-4.1">4.1</a>. AUTHENTICATION ............................................<a href="#page-10">10</a> |
| 47 |
<a href="#section-4.1.1">4.1.1</a>. Telnet Authentication ...................................<a href="#page-10">10</a> |
| 48 |
<a href="#section-4.1.2">4.1.2</a>. Telnet over TLS option ..................................<a href="#page-11">11</a> |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">da Cruz & Altman Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc2839">RFC 2839</a> Internet Kermit Service May 2000</span> |
| 55 |
|
| 56 |
|
| 57 |
<a href="#section-4.1.3">4.1.3</a>. Plaintext Authentication via Kermit REMOTE LOGIN ........<a href="#page-11">11</a> |
| 58 |
<a href="#section-4.1.4">4.1.4</a>. Plaintext Authentication via Command Prompt .............<a href="#page-11">11</a> |
| 59 |
<a href="#section-4.1.5">4.1.5</a>. Anonymous Login .........................................<a href="#page-12">12</a> |
| 60 |
<a href="#section-4.2">4.2</a>. ENCRYPTION (PRIVACY) ......................................<a href="#page-12">12</a> |
| 61 |
<a href="#section-4.2.1">4.2.1</a> Telnet Encryption .......................................<a href="#page-12">12</a> |
| 62 |
<a href="#section-4.2.2">4.2.2</a> Telnet Start_TLS ........................................<a href="#page-12">12</a> |
| 63 |
<a href="#section-5">5</a>. SERVICES ....................................................<a href="#page-13">13</a> |
| 64 |
<a href="#section-5.1">5.1</a>. Features for System Administrators ........................<a href="#page-13">13</a> |
| 65 |
<a href="#section-5.2">5.2</a>. Features for Users ........................................<a href="#page-14">14</a> |
| 66 |
<a href="#section-5.3">5.3</a>. User Interface ............................................<a href="#page-16">16</a> |
| 67 |
<a href="#section-6">6</a>. REFERENCES ..................................................<a href="#page-18">18</a> |
| 68 |
<a href="#section-7">7</a>. AUTHORS' ADDRESSES ..........................................<a href="#page-19">19</a> |
| 69 |
<a href="#section-8">8</a>. Full Copyright Statement ....................................<a href="#page-20">20</a> |
| 70 |
|
| 71 |
PREFACE |
| 72 |
|
| 73 |
This document describes an Internet Kermit Service (IKS) which |
| 74 |
provides an alternative to FTP for the transfer of files. This |
| 75 |
service is based upon both the TELNET protocol and the Kermit file |
| 76 |
transfer protocol. |
| 77 |
|
| 78 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. INTRODUCTION</span> |
| 79 |
|
| 80 |
The Internet Kermit Service: |
| 81 |
|
| 82 |
1. Provides direct access to Kermit file transfer and management |
| 83 |
services without requiring the user to first login to a shell |
| 84 |
account; |
| 85 |
|
| 86 |
2. Provides Kermit file transfer and management services to anonymous |
| 87 |
users; |
| 88 |
|
| 89 |
3. Provides services to all Telnet clients that support Kermit file |
| 90 |
transfer protocol via a simple, predictable, scriptable, and |
| 91 |
well-documented textual interface; |
| 92 |
|
| 93 |
4. Provides direct and tightly-coupled access to a Kermit server when |
| 94 |
requested via the Telnet Kermit Option [<a href="#ref-TKO" title=""Telnet Kermit Option"">TKO</a>]. |
| 95 |
|
| 96 |
This memo assumes knowledge of Transmission Control Protocol, the |
| 97 |
Telnet Protocol [<a href="#ref-TEL" title=""Telnet Protocol Specification"">TEL</a>], the Kermit File Transfer Protocol [<a href="#ref-KER" title=""Kermit, A File Transfer Protocol"">KER</a>,<a href="#ref-PRF" title=""Kermit Protocol - Formal Specification and Verification"">PRF</a>], |
| 98 |
Telnet Kermit Option [<a href="#ref-TKO" title=""Telnet Kermit Option"">TKO</a>], and the commands and features of Kermit |
| 99 |
software [<a href="#ref-CKB" title=""Using C-Kermit"">CKB</a>,<a href="#ref-CMG" title=""Using MS-DOS Kermit"">CMG</a>,<a href="#ref-K95" title=""Kermit 95"">K95</a>]. |
| 100 |
|
| 101 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 102 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 103 |
document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="#ref-BCP" title=""Key words for use in RFCs to Indicate Requirement Levels"">BCP</a>]. |
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">da Cruz & Altman Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc2839">RFC 2839</a> Internet Kermit Service May 2000</span> |
| 111 |
|
| 112 |
|
| 113 |
Definitions: |
| 114 |
|
| 115 |
Kermit server |
| 116 |
A software program that is ready to accept and act upon commands |
| 117 |
in the form of well-defined Kermit packets [<a href="#ref-KER" title=""Kermit, A File Transfer Protocol"">KER</a>]. |
| 118 |
|
| 119 |
Kermit client |
| 120 |
A software program that receives requests through its user |
| 121 |
interface from a human user (or a script or other source) and |
| 122 |
translates them to command packets, which it sends to a Kermit |
| 123 |
server, thus initiating a Kermit protocol transaction such as the |
| 124 |
transfer of one or more files. |
| 125 |
|
| 126 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. BACKGROUND</span> |
| 127 |
|
| 128 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. History</span> |
| 129 |
|
| 130 |
"Kermit" is the name of an extensible platform- and medium- |
| 131 |
independent file transfer and management protocol [<a href="#ref-KER" title=""Kermit, A File Transfer Protocol"">KER</a>,<a href="#ref-PRF" title=""Kermit Protocol - Formal Specification and Verification"">PRF</a>] and of a |
| 132 |
suite of communications software programs that implement it and |
| 133 |
integrate it with other communications functions [<a href="#ref-CMG" title=""Using MS-DOS Kermit"">CMG</a>,<a href="#ref-CKB" title=""Using C-Kermit"">CKB</a>,<a href="#ref-K95" title=""Kermit 95"">K95</a>]. |
| 134 |
|
| 135 |
The Kermit protocol was first developed at Columbia University in New |
| 136 |
York City in 1981 for transferring files without errors between |
| 137 |
diverse types of computers over potentially hostile communication |
| 138 |
links. Since 1981, the Kermit Project at Columbia University has |
| 139 |
expanded the protocol, developed communications software that |
| 140 |
implements it upon key platforms, and worked with volunteer |
| 141 |
programmers at other sites adapting Kermit protocol to other |
| 142 |
platforms or communication methods. The Kermit Project also serves |
| 143 |
as the central point of Kermit software development, support, |
| 144 |
information, and distribution throughout the world. |
| 145 |
|
| 146 |
Kermit software is now available for nearly every computer and |
| 147 |
operating system in existence. The major features of the most |
| 148 |
popular Kermit programs are: |
| 149 |
|
| 150 |
- Connection establishment and maintenance for a variety of |
| 151 |
connection methods including direct serial, dialup, TCP/IP, X.25, |
| 152 |
DECnet, and NETBIOS. |
| 153 |
|
| 154 |
- Terminal emulation. |
| 155 |
|
| 156 |
- Error-free transfer of both text and binary files, individually or |
| 157 |
in groups. |
| 158 |
|
| 159 |
- Character-set translation during both terminal emulation and |
| 160 |
text-mode file transfer -- a unique feature of Kermit software. |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">da Cruz & Altman Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc2839">RFC 2839</a> Internet Kermit Service May 2000</span> |
| 167 |
|
| 168 |
|
| 169 |
- Remote file management through the client/server protocol. |
| 170 |
|
| 171 |
- A powerful and portable scripting language allowing complete |
| 172 |
automation of any task that can be performed manually. |
| 173 |
|
| 174 |
Kermit's command and script language is consistent across all |
| 175 |
platforms and communication methods, thus offering a unified method |
| 176 |
for accomplishing a wide range of communication tasks manually or |
| 177 |
under script control. |
| 178 |
|
| 179 |
A single Kermit program combines the functions of many different |
| 180 |
programs such as uucp, cu, tip, telnet, rlogin, ftp, iconv, and |
| 181 |
expect: it is a Telnet and Rlogin client that can also transfer |
| 182 |
files; it is a file transfer program that can also convert character |
| 183 |
sets; it is a dialout program that can use dialing directories and |
| 184 |
understands country codes and area codes; it is fully scriptable; it |
| 185 |
offers both client/server and interactive modes of operation. In its |
| 186 |
desktop versions (particularly for DOS, Windows, and OS/2) it offers |
| 187 |
all the features of communications software that are usually lacking |
| 188 |
from Internet client software (key mapping, colors, scrollback, mouse |
| 189 |
functions, printer control, etc) |
| 190 |
|
| 191 |
Kermit software is widely used throughout the academic, government, |
| 192 |
and corporate spheres, both in the USA and internationally. |
| 193 |
|
| 194 |
In addition to the Kermit software developed and/or distributed by |
| 195 |
the Kermit Project at Columbia University, hundreds of other software |
| 196 |
products -- commercial, shareware, and freeware -- also include some |
| 197 |
level of support for the Kermit protocol. Thus there are hundreds, |
| 198 |
perhaps thousands, of independent and interoperable Kermit protocol |
| 199 |
implementations based upon the open Kermit protocol specification |
| 200 |
[<a href="#ref-KER" title=""Kermit, A File Transfer Protocol"">KER</a>]. |
| 201 |
|
| 202 |
The Internet has formed the primary mechanism by which users and |
| 203 |
developers of Kermit software have collaborated to produce feature |
| 204 |
and command sets that continually evolve to meet their needs as |
| 205 |
technology changes. |
| 206 |
|
| 207 |
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Motivation.</span> |
| 208 |
|
| 209 |
Kermit protocol and software makes connections from one computer to |
| 210 |
another and transfers data between them. Countless people "live" in |
| 211 |
Kermit all day long; as a customizable Telnet or Rlogin (or serial |
| 212 |
communication) client with a wide selection of terminal emulations |
| 213 |
and convenience features, it is their window onto the Internet. |
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">da Cruz & Altman Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc2839">RFC 2839</a> Internet Kermit Service May 2000</span> |
| 223 |
|
| 224 |
|
| 225 |
Others use it in more creative ways, including some that involve key |
| 226 |
parts of the Internet, e.g. in batch or cron jobs that update news or |
| 227 |
Web servers or fetch email, or to monitor routers, terminal servers, |
| 228 |
and hubs and dial pagers when faults are detected. It is used by |
| 229 |
vendors of telecommunications equipment for remote diagnosis, |
| 230 |
patching, and updates. Telecom managers often use Kermit scripts to |
| 231 |
configure PBXs, muxes, routers, or terminal servers. In the world of |
| 232 |
commerce, Kermit is widely used for financial transactions, EDI, |
| 233 |
medical claim submission, and so forth. It is used with mobile |
| 234 |
barcode readers in warehousing and inventory applications. It is |
| 235 |
found in US Postal Service sorting and scanning equipment. It |
| 236 |
connects many of the logistics and supply systems throughout the |
| 237 |
military. It is found in fast-food restaurant cash registers, |
| 238 |
milling and die-cutting machines, textile looms and cutters, printing |
| 239 |
presses, and medical diagnostic equipment. It was the communications |
| 240 |
backbone of the 1994 Brazilian national election -- the largest in |
| 241 |
history. |
| 242 |
|
| 243 |
And yet there has never been a strong, explicit connection of Kermit |
| 244 |
with the Internet. In the early years, Kermit acted as a kind of |
| 245 |
do-it-yourself network, enabling ordinary users to make connections |
| 246 |
that were not already there, and for some years was the predominant |
| 247 |
method of connecting a personal computer to the ARPAnet (e.g. by |
| 248 |
dialing a TAC). |
| 249 |
|
| 250 |
Nowadays, however, with so many of the world's computers on the |
| 251 |
Internet, the role of Kermit software and protocol is changing. |
| 252 |
Kermit users on the network would like to have the features, |
| 253 |
functions, and interface they are accustomed to -- especially the |
| 254 |
automation features -- available for use in settings where presently |
| 255 |
only tools like FTP are available -- and even more so in situations |
| 256 |
where standard software like FTP can't be used. |
| 257 |
|
| 258 |
An Internet Kermit Service can fill this role, and augment the data |
| 259 |
transfer power and flexibility of other Internet applications such as |
| 260 |
Web browsers: |
| 261 |
|
| 262 |
- Like FTP, Kermit provides a service that can be accessed from many |
| 263 |
different platforms with a consistent set of commands, but unlike |
| 264 |
FTP, these commands include programming constructions such as |
| 265 |
variables, arrays, looping and selection mechanisms, and local and |
| 266 |
remote procedure calls. |
| 267 |
|
| 268 |
- Like FTP, Kermit provides both text- and binary-mode data |
| 269 |
transfer, as well as file management capabilities. But Kermit |
| 270 |
also offers numerous features lacking from FTP, such as |
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">da Cruz & Altman Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc2839">RFC 2839</a> Internet Kermit Service May 2000</span> |
| 279 |
|
| 280 |
|
| 281 |
character-set translation, flexible file selection mechanisms, |
| 282 |
attribute preservation, and so on (see <a href="#section-5.3">Section 5.3</a> for a longer |
| 283 |
list). |
| 284 |
|
| 285 |
- Unlike standard FTP, Kermit can transfer data through multiple |
| 286 |
firewalls, proxies, and network address translators (NATs) on a |
| 287 |
single port. |
| 288 |
|
| 289 |
- Unlike FTP, Kermit can transfer data across a combination of |
| 290 |
transports (e.g. dial-up to a terminal server and thence to an |
| 291 |
Internet host). |
| 292 |
|
| 293 |
- Authentication and data transfer can take place over secure |
| 294 |
connections (mutually authenticated and encrypted) using |
| 295 |
established Telnet authentication and encryption options. |
| 296 |
|
| 297 |
- Unlike traditional Kermit use over Telnet, anonymous access is |
| 298 |
possible, and the considerable overhead of the intervening Telnet |
| 299 |
server and pseudoterminal service is eliminated. |
| 300 |
|
| 301 |
Until now the primary obstacles to an Internet Kermit Service have |
| 302 |
been: |
| 303 |
|
| 304 |
- Issues of authentication, privacy, and anonymous access. These |
| 305 |
have been addressed in our implementation, as described <a href="#section-4">Section 4</a> |
| 306 |
of this document. |
| 307 |
|
| 308 |
- Issues of coordination and control. A Kermit software program can |
| 309 |
be in any of several "modes": at its command prompt or menu, |
| 310 |
awaiting commands from the user; in terminal mode, in which the |
| 311 |
user's keystrokes are sent to the remote computer or service; or |
| 312 |
in protocol mode, in which two Kermit programs communicate via |
| 313 |
well-defined Kermit packets [<a href="#ref-KER" title=""Kermit, A File Transfer Protocol"">KER</a>]. Commands or operations valid |
| 314 |
in one mode do not necessarily work in another. Until now, it has |
| 315 |
been the user's responsibility to switch modes at one or both ends |
| 316 |
of the connection as needed. A companion document [<a href="#ref-TKO" title=""Telnet Kermit Option"">TKO</a>] to this |
| 317 |
one specifies a mechanism to closely couple the client and server |
| 318 |
via Telnet protocol negotiations, allowing each to know the |
| 319 |
other's state and to switch to the appropriate mode automatically |
| 320 |
so a valid and useful relationship obtains at all times. |
| 321 |
|
| 322 |
- Lack of a standard TCP port. The "registered" port 1649 was |
| 323 |
assigned by IANA for this purpose (27 September 1995) and is named |
| 324 |
"Kermit". (renamed from "Inspect".) |
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">da Cruz & Altman Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc2839">RFC 2839</a> Internet Kermit Service May 2000</span> |
| 335 |
|
| 336 |
|
| 337 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. THE INTERNET KERMIT SERVICE MODEL</span> |
| 338 |
|
| 339 |
The Internet Kermit Service (IKS) uses a standard Telnet [<a href="#ref-TEL" title=""Telnet Protocol Specification"">TEL</a>] |
| 340 |
connection, in which all Telnet rules apply. Unlike FTP, which |
| 341 |
requires additional TCP connections, IKS uses a single channel for |
| 342 |
both signaling and data transfer. The connection is multiplexed via |
| 343 |
(a) Telnet options, and (b) Kermit protocol messages. This allows |
| 344 |
existing Telnet clients that also support the Kermit protocol, |
| 345 |
whether or not they support the Telnet Kermit Option [<a href="#ref-TKO" title=""Telnet Kermit Option"">TKO</a>], to use |
| 346 |
the IKS and take advantage of all relevant Telnet options including |
| 347 |
authentication and encryption. |
| 348 |
|
| 349 |
The system Internet services daemon (e.g. inetd) waits for a |
| 350 |
connection on the Kermit socket (1649) and then starts the IKS on the |
| 351 |
new connection. The IKS performs the familiar Telnet negotiations |
| 352 |
including the Telnet Kermit option. Unlike a standard Telnet server, |
| 353 |
the IKS does not support the ability to present the user with an |
| 354 |
interactive system shell. The Kermit socket is used only for file |
| 355 |
transfer and management functions provided by Kermit file transfer |
| 356 |
protocol and the Kermit script language. |
| 357 |
|
| 358 |
Once the connection is established, the Telnet Kermit Option is |
| 359 |
negotiated in both directions. The results determine which of the |
| 360 |
following configurations is used by the Telnet client and Server: |
| 361 |
|
| 362 |
. Server-side Kermit Server (SKS) |
| 363 |
. Client-side Kermit Server (CKS) |
| 364 |
. No Kermit Server (NKS) |
| 365 |
|
| 366 |
Different procedures and functions apply to each configuration. The |
| 367 |
configuration may be changed at any time by Telnet Kermit Option |
| 368 |
subnegotiations, which assure that the Telnet client and server are |
| 369 |
always in compatible states. |
| 370 |
|
| 371 |
The three configurations are described in the following sections. |
| 372 |
|
| 373 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Server-Side Kermit Server</span> |
| 374 |
|
| 375 |
In the Server-Side Kermit Server (SKS) configuration, the Telnet |
| 376 |
server is the Kermit server and the Telnet client is the Kermit |
| 377 |
client. This configuration is used when both Telnet client and IKS |
| 378 |
support the Telnet Kermit Option and the IKS sends WILL KERMIT to the |
| 379 |
Telnet client and receives DO KERMIT from the Telnet client [<a href="#ref-TKO" title=""Telnet Kermit Option"">TKO</a>]. |
| 380 |
|
| 381 |
In this case, the IKS immediately starts a Kermit server and reports |
| 382 |
this to the Telnet client with a Telnet KERMIT START-SERVER |
| 383 |
subnegotiation. |
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">da Cruz & Altman Informational [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc2839">RFC 2839</a> Internet Kermit Service May 2000</span> |
| 391 |
|
| 392 |
|
| 393 |
The SKS configuration is appropriate when the user wishes to interact |
| 394 |
only with the Telnet client's commands or menus. |
| 395 |
|
| 396 |
If authentication was not performed with one of the Telnet |
| 397 |
Authentication Option protocols, the Kermit server rejects all Kermit |
| 398 |
protocol operations (except REMOTE LOGIN, REMOTE HELP, REMOTE EXIT, |
| 399 |
BYE, or FINISH -- that is, the ones that request help, that log in, |
| 400 |
that close the connection, or that change the status of the |
| 401 |
connection) until: |
| 402 |
|
| 403 |
- A Kermit REMOTE LOGIN command successfully authenticates the user; |
| 404 |
|
| 405 |
- The login retry limit is reached; |
| 406 |
|
| 407 |
- A Kermit BYE or REMOTE EXIT command is received, which closes the |
| 408 |
connection; |
| 409 |
|
| 410 |
- A Kermit FINISH command or a Telnet KERMIT REQ-KERMIT-STOP |
| 411 |
subnegotiation is received to request the IKS exit from Kermit |
| 412 |
server mode. At this point, the IKS can either exit and close the |
| 413 |
connection or issue an interactive login prompt, depending on how |
| 414 |
it was started or configured by the system administrator. |
| 415 |
|
| 416 |
Once the user is authenticated: |
| 417 |
|
| 418 |
- The Telnet client configures itself for Kermit client/server |
| 419 |
operation, with itself as the Kermit client, communicating with |
| 420 |
the server only by Kermit packets, and optionally adjusting its |
| 421 |
menus or commands to eliminate functions (such as terminal |
| 422 |
emulation) that make no sense in this context. |
| 423 |
|
| 424 |
- The relationship persists until the Telnet client and IKS agree to |
| 425 |
terminate the Kermit server via Kermit protocol commands (BYE, |
| 426 |
FINISH, or REMOTE EXIT), or by Telnet Kermit Option |
| 427 |
subnegotiation, or by closing the connection. |
| 428 |
|
| 429 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Client-Side Kermit Server</span> |
| 430 |
|
| 431 |
In the Client-Side Kermit Server (CKS) configuration, the Telnet |
| 432 |
server is the Kermit client, and the Telnet client is the Kermit |
| 433 |
server. This configuration is used when the IKS has sent WONT KERMIT |
| 434 |
or SB KERMIT STOP-SERVER, and the Telnet Client has sent WILL KERMIT |
| 435 |
and SB KERMIT START-SERVER, indicating that it is prepared to accept |
| 436 |
and process Kermit protocol packets. |
| 437 |
|
| 438 |
In the CKS configuration, the Telnet client assumes the role of |
| 439 |
Kermit server by virtue of its ability to recognize and process |
| 440 |
Kermit protocol packets in its terminal emulator. Thus the Telnet |
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">da Cruz & Altman Informational [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc2839">RFC 2839</a> Internet Kermit Service May 2000</span> |
| 447 |
|
| 448 |
|
| 449 |
client must not send WILL KERMIT or the KERMIT START-SERVER |
| 450 |
subnegotiation unless its terminal emulator is capable of recognizing |
| 451 |
Kermit packets. |
| 452 |
|
| 453 |
If the IKS is at top command level (as opposed to executing a |
| 454 |
script), or when it reaches top level after finishing a script, it |
| 455 |
issues its interactive command prompt. |
| 456 |
|
| 457 |
At this point, the user may type commands or send scripted commands |
| 458 |
to the IKS command prompt. When a data-transfer command (such as |
| 459 |
SEND) is issued by the user at the IKS prompt, a Kermit packet is |
| 460 |
transmitted and recognized by the Telnet client, causing it to |
| 461 |
automatically perform the requested action (e.g. receive a file), and |
| 462 |
then resume its previous mode (terminal emulation or script |
| 463 |
execution) when the data transfer is complete. |
| 464 |
|
| 465 |
Thus, in the CKS configuration, data transfers are initiated by the |
| 466 |
IKS rather than by the Telnet client. This configuration is useful |
| 467 |
when the user prefers the command interface or repertoire of the |
| 468 |
server to that of the client. |
| 469 |
|
| 470 |
If the IKS sends a Telnet KERMIT START-SERVER subnegotiation, the |
| 471 |
relationship switches automatically to Server-Side Kermit Server |
| 472 |
(<a href="#section-3.1">Section 3.1</a>), in which the Telnet client is the Kermit client and |
| 473 |
the Telnet server is the Kermit server. |
| 474 |
|
| 475 |
If the Telnet client sends a KERMIT STOP-SERVER subnegotiation, the |
| 476 |
connection switches to No Kermit Server (<a href="#section-3.3">Section 3.3</a>) and the IKS |
| 477 |
issues its command prompt. At this point, neither side is a Kermit |
| 478 |
server, and both sides may optionally disable Kermit protocol |
| 479 |
commands. Subsequent user action can designate one side or the other |
| 480 |
as the Kermit server, as desired. |
| 481 |
|
| 482 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. No Kermit Server</span> |
| 483 |
|
| 484 |
If both Telnet client and IKS send WONT KERMIT or SB KERMIT STOP- |
| 485 |
SERVER, or if the Kermit client and server are connected across |
| 486 |
multiple hosts or transports, thus precluding end-to-end Telnet |
| 487 |
negotiation, a Kermit server is not known to be available. In the |
| 488 |
KERMIT STOP-SERVER case, the Kermit partners can later switch back to |
| 489 |
SKS or CKS, but in the other two cases, there is no such signaling |
| 490 |
and loose coupling characterizes the entire session. |
| 491 |
|
| 492 |
In the No Kermit Server (NKS) configuration, the IKS presents a |
| 493 |
command prompt to the Telnet client. As in the Client-Side Kermit |
| 494 |
Server configuration, plain-text commands are issued to the IKS. |
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">da Cruz & Altman Informational [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc2839">RFC 2839</a> Internet Kermit Service May 2000</span> |
| 503 |
|
| 504 |
|
| 505 |
In the loosely coupled NKS configuration, the Telnet client does not |
| 506 |
know the state of the Telnet server, and so can not automatically |
| 507 |
adjust its commands and menus to present only valid choices, or |
| 508 |
automatically change its state to complement the server's; it is the |
| 509 |
user's responsibility to assure that the "mode" (command prompt, |
| 510 |
terminal emulation, server command wait) of each Kermit partner is |
| 511 |
appropriate for each action. Thus an Internet Kermit Server appears |
| 512 |
as an ordinary remote Kermit program to any Telnet client that does |
| 513 |
not implement the Telnet Kermit Option, or in which this feature is |
| 514 |
disabled or can not be used. |
| 515 |
|
| 516 |
The NKS configuration allows successful manual operation of the IKS |
| 517 |
through Telnet clients that do not support the Telnet Kermit Option. |
| 518 |
The Telnet client might or might not support Kermit "autodownload" |
| 519 |
and "autoupload"; if it does not, then the user is forced to manually |
| 520 |
issue command on both sides of the connection in the traditional and |
| 521 |
familiar manner [<a href="#ref-CKB" title=""Using C-Kermit"">CKB</a>,<a href="#ref-CMG" title=""Using MS-DOS Kermit"">CMG</a>,<a href="#ref-K95" title=""Kermit 95"">K95</a>]. |
| 522 |
|
| 523 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. SECURITY CONSIDERATIONS</span> |
| 524 |
|
| 525 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. AUTHENTICATION</span> |
| 526 |
|
| 527 |
Authentication is provided via one or more of the following methods: |
| 528 |
|
| 529 |
- The Telnet AUTHENTICATION option; |
| 530 |
|
| 531 |
- The Telnet START_TLS option; |
| 532 |
|
| 533 |
- Plaintext userid/password verification. |
| 534 |
|
| 535 |
<span class="h4"><a class="selflink" id="section-4.1.1" href="#section-4.1.1">4.1.1</a>. Telnet Authentication option</span> |
| 536 |
|
| 537 |
The use of one of the many Telnet authentication option methods |
| 538 |
removes the need to transmit passwords in plaintext across public |
| 539 |
networks. In addition, the exchange of user authentication |
| 540 |
information often provides a shared secret that can be used with the |
| 541 |
Telnet Encryption Option protocols to encrypt the connection in one |
| 542 |
or both directions. |
| 543 |
|
| 544 |
Telnet authentication may also be used in conjunction with the Telnet |
| 545 |
START_TLS option to negotiate end user identity over the encrypted |
| 546 |
and host authenticated TLS channel. |
| 547 |
|
| 548 |
The IKS currently supports Kerberos 4, Kerberos 5, Secure Remote |
| 549 |
Password and Microsoft NTLM authentication methods via the Telnet |
| 550 |
AUTH option. |
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">da Cruz & Altman Informational [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc2839">RFC 2839</a> Internet Kermit Service May 2000</span> |
| 559 |
|
| 560 |
|
| 561 |
<span class="h4"><a class="selflink" id="section-4.1.2" href="#section-4.1.2">4.1.2</a>. Telnet over TLS option</span> |
| 562 |
|
| 563 |
The Telnet START_TLS option provides for the negotiation and |
| 564 |
establishment of a TLS version 1 session after the initial telnet |
| 565 |
connection. The TLS connection provides host to client |
| 566 |
authentication via the use of X.509 certificate chains. TLS also |
| 567 |
supports optional client to host authentication using host verified |
| 568 |
X.509 certificates which may be used to authenticate a userid |
| 569 |
provided by the client or be mapped to a userid based upon properties |
| 570 |
of the certificate. |
| 571 |
|
| 572 |
<span class="h4"><a class="selflink" id="section-4.1.3" href="#section-4.1.3">4.1.3</a>. Plaintext Authentication via Kermit REMOTE LOGIN</span> |
| 573 |
|
| 574 |
In the Server-Side Kermit Server configuration, if the client is not |
| 575 |
yet authenticated, the client must log in using a REMOTE LOGIN |
| 576 |
command, in which a Kermit packet containing user ID and password in |
| 577 |
clear text is sent from the Telnet client to the Telnet server, which |
| 578 |
then calls upon local mechanisms to authenticate the user. Any |
| 579 |
packets other than login (or REMOTE HELP, REMOTE EXIT, FINISH, or |
| 580 |
BYE) packets are rejected (returned with an error message) until the |
| 581 |
user is authenticated. If the number of unsuccessful login attempts |
| 582 |
exceeds the limit, the connection is closed. Many Kermit client |
| 583 |
programs support this login method already. |
| 584 |
|
| 585 |
This method should be avoided whenever possible. If plaintext |
| 586 |
passwords are used, they should only be sent after the Telnet START- |
| 587 |
TLS option has been negotiated (see 4.2.2). Otherwise, passwords are |
| 588 |
open to packet sniffing. |
| 589 |
|
| 590 |
<span class="h4"><a class="selflink" id="section-4.1.4" href="#section-4.1.4">4.1.4</a>. Plaintext Authentication via Command Prompt</span> |
| 591 |
|
| 592 |
In the Client-Side Kermit Server and No Kermit Server configurations, |
| 593 |
the server presents the user with a plain-text interactive interface |
| 594 |
that begins with the server issuing "Username:" and "Password:" |
| 595 |
prompts, just as if the user were logging in to a multiuser |
| 596 |
timesharing system such as VMS or UNIX. When a password is not |
| 597 |
required an empty response can be given. Invalid username-password |
| 598 |
combinations result in a new series of prompts up to the login retry |
| 599 |
limit, and then disconnection. |
| 600 |
|
| 601 |
This method should be avoided whenever possible. If plaintext |
| 602 |
passwords are used, they should only be sent after the Telnet START- |
| 603 |
TLS option has been negotiated (see 4.2.2). Otherwise, passwords are |
| 604 |
open to packet sniffing. |
| 605 |
|
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">da Cruz & Altman Informational [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc2839">RFC 2839</a> Internet Kermit Service May 2000</span> |
| 615 |
|
| 616 |
|
| 617 |
<span class="h4"><a class="selflink" id="section-4.1.5" href="#section-4.1.5">4.1.5</a>. Anonymous Login</span> |
| 618 |
|
| 619 |
When the username is "anonymous" or "ftp", the IKS behaves like an |
| 620 |
anonymous ftp server, in a manner appropriate to the underlying |
| 621 |
platform. In UNIX, for example, access is restricted to a designated |
| 622 |
area of the file system. A password might or might not be required, |
| 623 |
according to the preference of the site administrator. |
| 624 |
|
| 625 |
If privacy is desired the Telnet START-TLS option should be used (see |
| 626 |
4.2.2). |
| 627 |
|
| 628 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. ENCRYPTION (PRIVACY)</span> |
| 629 |
|
| 630 |
As the Internet becomes ever more public and susceptible to |
| 631 |
eavesdropping, it becomes increasingly necessary to provide methods |
| 632 |
for private access to services. Telnet provides two such mechanisms: |
| 633 |
|
| 634 |
. Telnet Encryption option |
| 635 |
. Telnet START-TLS option |
| 636 |
|
| 637 |
<span class="h4"><a class="selflink" id="section-4.2.1" href="#section-4.2.1">4.2.1</a>. Telnet Encryption option</span> |
| 638 |
|
| 639 |
The Telnet Encryption option, although it has never achieved RFC |
| 640 |
status, has been used for years in conjunction with the Telnet Auth |
| 641 |
option in Telnet clients and servers that support Kerberos 4, |
| 642 |
Kerberos 5, Secure Remote Password, and others. The IKS currently |
| 643 |
supports the following encryption methods under the Telnet Encryption |
| 644 |
option: |
| 645 |
|
| 646 |
. cast128_ofb64 |
| 647 |
. cast5_40_ofb64 |
| 648 |
. des_ofb64 |
| 649 |
. cast128_cfb64 |
| 650 |
. cast5_40_cfb64 |
| 651 |
. des_cfb64 |
| 652 |
|
| 653 |
<span class="h4"><a class="selflink" id="section-4.2.2" href="#section-4.2.2">4.2.2</a>. Telnet over TLS option</span> |
| 654 |
|
| 655 |
Transport Layer Security (TLS), the successor to Secure Sockets Layer |
| 656 |
(SSL), provides methods to implement Server authentication, Client |
| 657 |
authentication, and Transport Layer encryption. Unlike Telnet |
| 658 |
Encryption, Start-TLS does not require the use of Telnet |
| 659 |
Authentication in order to provide a private channel. This means |
| 660 |
that it can be used in conjunction with plaintext passwords and |
| 661 |
anonymous connections. |
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">da Cruz & Altman Informational [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc2839">RFC 2839</a> Internet Kermit Service May 2000</span> |
| 671 |
|
| 672 |
|
| 673 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. SERVICES</span> |
| 674 |
|
| 675 |
The Internet Kermit Service includes features for both users and |
| 676 |
system administrators. The IKS is incorporated into the 7.0 release |
| 677 |
of Columbia University's C-Kermit software, which is the "master" |
| 678 |
Kermit software program in terms of features and command language. |
| 679 |
An overview of C-Kermit can be found at: |
| 680 |
|
| 681 |
<a href="http://www.columbia.edu/kermit/ckermit.html">http://www.columbia.edu/kermit/ckermit.html</a> |
| 682 |
<a href="http://www.kermit-project.org/ckermit.html">http://www.kermit-project.org/ckermit.html</a> |
| 683 |
|
| 684 |
When C-Kermit is employed as an Internet Kermit Service, it may offer |
| 685 |
all its functions to "real" users (those who are authenticated as |
| 686 |
specific users), and a safe subset of its functions to anonymous |
| 687 |
users. |
| 688 |
|
| 689 |
The Internet Kermit Service resembles an FTP server in that it |
| 690 |
performs its own authentication and uses a well-defined protocol to |
| 691 |
communicate with its client, but differs from the FTP server by also |
| 692 |
offering (at the system manager's discretion) an interactive user |
| 693 |
interface to the Telnet client when it is in terminal mode. It also |
| 694 |
differs from FTP in restricting all protocol messages and data |
| 695 |
transfer to a single socket connection. |
| 696 |
|
| 697 |
An IKS has been deployed at Columbia University for worldwide public |
| 698 |
access to the Kermit FTP site: |
| 699 |
|
| 700 |
telnet://kermit.columbia.edu:1649/ |
| 701 |
telnet://ftp.kermit-project.org:1649/ |
| 702 |
|
| 703 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Features for System Administrators</span> |
| 704 |
|
| 705 |
The system administrator can supply IKS configuration parameters as |
| 706 |
command-line options or in a configuration file, or both in |
| 707 |
combination. Such parameters include: |
| 708 |
|
| 709 |
. Whether anonymous logins are allowed. |
| 710 |
|
| 711 |
. The file system or root directory to which anonymous users are |
| 712 |
restricted. |
| 713 |
|
| 714 |
. Specification of permissions and other attributes to be assigned |
| 715 |
to files uploaded by anonymous users. |
| 716 |
|
| 717 |
. Whether to make session entries in system logs. |
| 718 |
|
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">da Cruz & Altman Informational [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc2839">RFC 2839</a> Internet Kermit Service May 2000</span> |
| 727 |
|
| 728 |
|
| 729 |
. Specific services to disable: reception of files, sending of |
| 730 |
files, sending of email, printing, changing of directories, |
| 731 |
getting directory listings, deleting files, etc (see next |
| 732 |
section). |
| 733 |
|
| 734 |
. Whether access to the interactive command prompt is allowed. |
| 735 |
|
| 736 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Features for Users</span> |
| 737 |
|
| 738 |
The IKS supports a wide range of services, including, but not limited |
| 739 |
to, the following: |
| 740 |
|
| 741 |
. Authentication as a real user or anonymously. |
| 742 |
|
| 743 |
. Transmission of files to which read access is allowed. |
| 744 |
|
| 745 |
. Reception of files into directories or devices to which write |
| 746 |
access is allowed. |
| 747 |
|
| 748 |
. The ability to display a file on the client's screen. |
| 749 |
|
| 750 |
. Ability to list files. |
| 751 |
|
| 752 |
. Ability to change its working (default) directory. |
| 753 |
|
| 754 |
. Ability to delete files to which write or delete access is |
| 755 |
allowed. |
| 756 |
|
| 757 |
. Ability to rename and copy files |
| 758 |
|
| 759 |
. Ability to create and remove directories. |
| 760 |
|
| 761 |
. The ability to route received files to a specified printer, or to |
| 762 |
send them as email to a specified address list. |
| 763 |
|
| 764 |
. Client control of server parameter settings, within limits |
| 765 |
established by the server system administrator. |
| 766 |
|
| 767 |
. Transmission of variables from client to server or vice versa. |
| 768 |
|
| 769 |
. Remote and local script execution. |
| 770 |
|
| 771 |
. Remote and local procedure execution. |
| 772 |
|
| 773 |
|
| 774 |
|
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">da Cruz & Altman Informational [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc2839">RFC 2839</a> Internet Kermit Service May 2000</span> |
| 783 |
|
| 784 |
|
| 785 |
File transfer features include: |
| 786 |
|
| 787 |
. Kermit text-mode transfers incorporate not only record-format |
| 788 |
conversion, but also character-set translation; |
| 789 |
|
| 790 |
. Kermit can switch automatically between text and binary mode on a |
| 791 |
per-file basis when sending groups of files. |
| 792 |
|
| 793 |
. A selection of file collision options, including "make backup copy |
| 794 |
of existing file and accept incoming file", "reject incoming |
| 795 |
file", "accept incoming file only if newer than existing file", |
| 796 |
etc. |
| 797 |
|
| 798 |
. Numerous methods for selecting the files to be transferred, |
| 799 |
including pattern matching, lists of filenames (or patterns), |
| 800 |
exception lists, date and/or size ranges, etc. |
| 801 |
|
| 802 |
. Filename conversion and file renaming. |
| 803 |
|
| 804 |
. Automatic directory creation if elected and enabled. |
| 805 |
|
| 806 |
. Standard mechanisms for directory traversal, allowing transmission |
| 807 |
of entire directory trees or other file hierarchies even between |
| 808 |
unlike file systems such as VMS, UNIX, and Windows. |
| 809 |
|
| 810 |
. Atomic file movement: optionally, the source file can be deleted |
| 811 |
(or renamed, or moved) when and only when it has been transferred |
| 812 |
successfully. |
| 813 |
|
| 814 |
. Kermit can retain file attributes including time stamps and |
| 815 |
permissions (at the user's or system administrator's discretion), |
| 816 |
even between unlike platforms; |
| 817 |
|
| 818 |
. Recovery of interrupted transfers from the point of failure. |
| 819 |
|
| 820 |
. File-transfer pipes and filters. |
| 821 |
|
| 822 |
Script programming features include: |
| 823 |
|
| 824 |
. Macros with parameter substitution. |
| 825 |
|
| 826 |
. Built-in and user-defined variables and arrays, with global or |
| 827 |
local scope. |
| 828 |
|
| 829 |
|
| 830 |
|
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">da Cruz & Altman Informational [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc2839">RFC 2839</a> Internet Kermit Service May 2000</span> |
| 839 |
|
| 840 |
|
| 841 |
. Built-in and user-defined functions. Built-in functions include: |
| 842 |
|
| 843 |
- String functions |
| 844 |
- Arithmetic functions |
| 845 |
- Date / time functions |
| 846 |
- File functions |
| 847 |
|
| 848 |
. Input search for multiple simultaneous targets. |
| 849 |
|
| 850 |
. IF-ELSE, WHILE, FOR, SWITCH, GOTO, C-like block structure. |
| 851 |
|
| 852 |
. Every command returns a completion status that may be tested and |
| 853 |
used as a basis for subsequent actions. |
| 854 |
|
| 855 |
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. User Interface</span> |
| 856 |
|
| 857 |
The Internet Kermit Service uses the Kermit command and script |
| 858 |
language, as implemented in Columbia University's C-Kermit |
| 859 |
communication software [<a href="#ref-CKB" title=""Using C-Kermit"">CKB</a>]. This program and its command language |
| 860 |
are portable to all known varieties of UNIX, as well as to Windows |
| 861 |
95/98/NT, OS/2, Digital (Open)VMS, Stratus VOS, Data General AOS/VS, |
| 862 |
Plan 9, OS-9, QNX, the Commodore Amiga, and other platforms. The |
| 863 |
C-Kermit command language is a superset of that of other Kermit |
| 864 |
software programs including MS-DOS Kermit for DOS and Windows 3.x, |
| 865 |
IBM Mainframe Kermit for VM/CMS, MVS/TSO, CICS, and MUSIC, PDP-11 |
| 866 |
Kermit for RT-11, RSTS/E, RSX-11, and IAS, and dozens of other Kermit |
| 867 |
programs. |
| 868 |
|
| 869 |
It is far beyond the scope of this document to enumerate, let alone |
| 870 |
describe, the commands and services of C-Kermit; this is the subject |
| 871 |
of a 600-page book [<a href="#ref-CKB" title=""Using C-Kermit"">CKB</a>], augmented by hundreds of pages of online |
| 872 |
material. A brief overview is included here. |
| 873 |
|
| 874 |
Commands are based on English words. There is no plan at present to |
| 875 |
support other natural languages (Italian, Portuguese, Norwegian, |
| 876 |
Russian, Hebrew, Japanese, Cherokee, etc) as alternative bases for |
| 877 |
command words, since this would reduce the portability of scripts. |
| 878 |
However, since the command language includes a macro capability, |
| 879 |
macros may be defined to provide selected commands in different |
| 880 |
languages if desired. |
| 881 |
|
| 882 |
Certain commands can apply either locally or remotely, for example |
| 883 |
"CD" (Change Directory). The convention is to prefix the command |
| 884 |
with the word REMOTE if it is to apply remotely. Example: "cd foo" |
| 885 |
changes to the "foo" directory on the computer where the command was |
| 886 |
given; "remote cd foo" sends a Kermit packet to the Kermit server |
| 887 |
requesting it to change its directory to "foo". The commands in this |
| 888 |
category include: |
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">da Cruz & Altman Informational [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc2839">RFC 2839</a> Internet Kermit Service May 2000</span> |
| 895 |
|
| 896 |
|
| 897 |
ASSIGN <variable> <value> Assign a value to a variable. |
| 898 |
CD <directory> Change working directory. |
| 899 |
COPY <files> <destination> Copy file(s) |
| 900 |
DELETE <files> Delete file(s) |
| 901 |
DIRECTORY [ <pattern> ] List file(s) |
| 902 |
EXIT Exit |
| 903 |
HELP [ <topic-or-command> ] Display help text |
| 904 |
MKDIR <directory> Create a directory |
| 905 |
PRINT <files> Print file(s) |
| 906 |
PWD Print working directory |
| 907 |
RENAME <old> <new> Rename file(s) |
| 908 |
RMDIR <directory> Remove a directory |
| 909 |
SET <parameter> <value> Change a parameter's value |
| 910 |
TYPE <file> Display the contents of a file |
| 911 |
|
| 912 |
As a convenience, REMOTE commands also have short synonyms: RASSIGN, |
| 913 |
RCD, RCOPY, RDELETE, and so forth. |
| 914 |
|
| 915 |
The basic file transfer commands are: |
| 916 |
|
| 917 |
SEND [ modifiers ] <files> Send file(s) (to server) |
| 918 |
GET [ modifiers ] <files> Get file(s) (from server) |
| 919 |
|
| 920 |
These commands take a file name, pattern, or list, plus various |
| 921 |
optional modifiers, including transfer mode specifiers (text, |
| 922 |
binary), file selectors (date, size, exception list), aliasing, name |
| 923 |
and path options, disposition specifiers, and so on. |
| 924 |
|
| 925 |
In addition to the commands listed above, the following commands are |
| 926 |
sent by the client to the server: |
| 927 |
|
| 928 |
REMOTE QUERY Get value of variable or procedure |
| 929 |
BYE Log out and close the connection |
| 930 |
FINISH Request the server leave server mode |
| 931 |
|
| 932 |
Like all Kermit client/server commands, these can be disabled if |
| 933 |
desired. |
| 934 |
|
| 935 |
Of course there are numerous other commands with purely local effect, |
| 936 |
such as the many scripting commands. These, plus all the commands |
| 937 |
above, are fully documented in [<a href="#ref-CKB" title=""Using C-Kermit"">CKB</a>]. The repertoire grows over |
| 938 |
time, but never in a way that invalidates existing scripts. |
| 939 |
|
| 940 |
The system administrator can allow or forbid access to any of these |
| 941 |
features, and to the command language as a whole. In the latter |
| 942 |
case, the IKS may be accessed only as a Kermit server, by giving |
| 943 |
commands to the client. |
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">da Cruz & Altman Informational [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc2839">RFC 2839</a> Internet Kermit Service May 2000</span> |
| 951 |
|
| 952 |
|
| 953 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. REFERENCES</span> |
| 954 |
|
| 955 |
[<a id="ref-TKO">TKO</a>] Altman, J. and F. da Cruz, "Telnet Kermit Option", <a href="./rfc2840">RFC 2840</a>, |
| 956 |
May 2000. |
| 957 |
|
| 958 |
[<a id="ref-BCP">BCP</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement |
| 959 |
Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 960 |
|
| 961 |
[<a id="ref-KER">KER</a>] da Cruz, Frank, "Kermit, A File Transfer Protocol", Digital |
| 962 |
Press/ Butterworth Heinemann, Newton, MA (1987). 379 pages, |
| 963 |
ISBN 0-932376-88-6. |
| 964 |
|
| 965 |
[<a id="ref-CKB">CKB</a>] da Cruz, Frank, and Christine M. Gianone, "Using C-Kermit", |
| 966 |
Second Edition, Digital Press / Butterworth-Heinemann, Woburn, |
| 967 |
MA (1997). 622 pages, ISBN 1-55558-164-1. |
| 968 |
|
| 969 |
[<a id="ref-CMG">CMG</a>] Gianone, Christine M., "Using MS-DOS Kermit", Second Edition, |
| 970 |
Digital Press / Butterworth-Heinemann, Woburn, MA (1992). 345 |
| 971 |
pages, ISBN 1-55558-082-3. |
| 972 |
|
| 973 |
[<a id="ref-K95">K95</a>] Gianone, Christine M., and Frank da Cruz, "Kermit 95", Manning |
| 974 |
Publications, Greenwich CT, (1996). 88 pages, ISBN 1-884777- |
| 975 |
14-7. |
| 976 |
|
| 977 |
[<a id="ref-PRF">PRF</a>] Huggins, James K., "Kermit Protocol - Formal Specification and |
| 978 |
Verification", in Boerger, E., "Specification and Validation |
| 979 |
Methods", Oxford University Press (1995). ISBN 0-19-853854-5. |
| 980 |
|
| 981 |
[<a id="ref-FTP">FTP</a>] Postel, J. and J. Reynolds, "File Transfer Protocol (FTP)", STD |
| 982 |
9, <a href="./rfc959">RFC 959</a>, October 1985. |
| 983 |
|
| 984 |
[<a id="ref-TEL">TEL</a>] Postel, J. and J. Reynolds, "Telnet Protocol Specification", |
| 985 |
STD 8, <a href="./rfc854">RFC854</a>, May 1983, et seq.; "Telnet Option |
| 986 |
Specification", STD 8, <a href="./rfc855">RFC855</a>, May 1983, et seq. |
| 987 |
|
| 988 |
[<a id="ref-IAN">IAN</a>] Internet Assigned Numbers Authority: |
| 989 |
<a href="http://www.iana.org/numbers.html">http://www.iana.org/numbers.html</a> |
| 990 |
<a href="http://www.iana.org/assignment/port-numbers">http://www.iana.org/assignment/port-numbers</a> |
| 991 |
|
| 992 |
|
| 993 |
|
| 994 |
|
| 995 |
|
| 996 |
|
| 997 |
|
| 998 |
|
| 999 |
|
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">da Cruz & Altman Informational [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc2839">RFC 2839</a> Internet Kermit Service May 2000</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. AUTHORS' ADDRESSES</span> |
| 1010 |
|
| 1011 |
Frank da Cruz |
| 1012 |
|
| 1013 |
EMail: [email protected] |
| 1014 |
|
| 1015 |
|
| 1016 |
Jeffrey E. Altman |
| 1017 |
|
| 1018 |
EMail:[email protected] |
| 1019 |
|
| 1020 |
|
| 1021 |
The Kermit Project |
| 1022 |
Columbia University |
| 1023 |
612 West 115th Street |
| 1024 |
New York NY 10025-7799 |
| 1025 |
USA |
| 1026 |
<a href="http://www.columbia.edu/kermit/">http://www.columbia.edu/kermit/</a> |
| 1027 |
<a href="http://www.kermit-project.org/">http://www.kermit-project.org/</a> |
| 1028 |
|
| 1029 |
|
| 1030 |
|
| 1031 |
|
| 1032 |
|
| 1033 |
|
| 1034 |
|
| 1035 |
|
| 1036 |
|
| 1037 |
|
| 1038 |
|
| 1039 |
|
| 1040 |
|
| 1041 |
|
| 1042 |
|
| 1043 |
|
| 1044 |
|
| 1045 |
|
| 1046 |
|
| 1047 |
|
| 1048 |
|
| 1049 |
|
| 1050 |
|
| 1051 |
|
| 1052 |
|
| 1053 |
|
| 1054 |
|
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">da Cruz & Altman Informational [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc2839">RFC 2839</a> Internet Kermit Service May 2000</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Full Copyright Statement</span> |
| 1066 |
|
| 1067 |
Copyright (C) The Internet Society (2000). All Rights Reserved. |
| 1068 |
|
| 1069 |
This document and translations of it may be copied and furnished to |
| 1070 |
others, and derivative works that comment on or otherwise explain it |
| 1071 |
or assist in its implementation may be prepared, copied, published |
| 1072 |
and distributed, in whole or in part, without restriction of any |
| 1073 |
kind, provided that the above copyright notice and this paragraph are |
| 1074 |
included on all such copies and derivative works. However, this |
| 1075 |
document itself may not be modified in any way, such as by removing |
| 1076 |
the copyright notice or references to the Internet Society or other |
| 1077 |
Internet organizations, except as needed for the purpose of |
| 1078 |
developing Internet standards in which case the procedures for |
| 1079 |
copyrights defined in the Internet Standards process must be |
| 1080 |
followed, or as required to translate it into languages other than |
| 1081 |
English. |
| 1082 |
|
| 1083 |
The limited permissions granted above are perpetual and will not be |
| 1084 |
revoked by the Internet Society or its successors or assigns. |
| 1085 |
|
| 1086 |
This document and the information contained herein is provided on an |
| 1087 |
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING |
| 1088 |
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING |
| 1089 |
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION |
| 1090 |
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF |
| 1091 |
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 1092 |
|
| 1093 |
Acknowledgement |
| 1094 |
|
| 1095 |
Funding for the RFC Editor function is currently provided by the |
| 1096 |
Internet Society. |
| 1097 |
|
| 1098 |
|
| 1099 |
|
| 1100 |
|
| 1101 |
|
| 1102 |
|
| 1103 |
|
| 1104 |
|
| 1105 |
|
| 1106 |
|
| 1107 |
|
| 1108 |
|
| 1109 |
|
| 1110 |
|
| 1111 |
|
| 1112 |
|
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
da Cruz & Altman Informational [Page 20] |
| 1117 |
</pre> |