The Kermit Project |
612 West 115th Street, New York NY 10025 USA • firstname.lastname@example.org
Most recent update: Sat Feb 20 09:53:59 2010
HERE. The original FAQ is organized chronologically; this new one is organized by topic and contains mainly just links to other pages. For example:
This document pertains to Kermit "as a whole". Major Kermit programs, in turn, have their own specific FAQs, e.g.:
Kermit 95 or MS-DOS Kermit, as appropriate. If you want to transfer files, you'll need two Kermit programs, one for each end of the connection. For example, if you want to make a connection from Windows XP to a Sun Solaris server, you'll need Kermit 95 for Windows and C-Kermit for Solaris.
Here's a quick overview:
But that's OK since almost all access nowadays is through our website:
which provides quick access to our most popular items, such as:
But there are lots more, some of them dating back a decade or two. A concise (but long) list is here:
The list is sorted by the contents of the "Machine" column. "Prefix" refers to the filename prefix, "Tape" refers to the subdirectory of the Kermit FTP site. Here's an example:
Prefix, Operating Program Program Released Tape Machine System Language Version yy/mm/dd Contributor MU D Honeywell MULTICS PL/I 2.0h 84/09/20 Oakland U
Kermit 2.0h for Honeywell MULTICS, written in PL/I at Oakland University, released 20 September 1984, is in the kermit/d directory of the FTP site, with filename prefix "mu". Even though the Prefix and Tape designators are listed in uppercase, you must enter them in lowercase because the FTP (and Web) site is now Unix-based (originally it was on a DECSYSTEM-20 where filenames were case-independent but shown in upper case). So to get the MULTICS version of Kermit, you would use FTP something like this:
$ mkdir multics (create a directory and cd to it) $ cd multics $ ftp kermit.columbia.edu (make the FTP connection) Name: anonymous (log in as user 'anonymous') Password: email@example.com (supply your actual email address) ftp> cd kermit/d (change directory to kermit/d) ftp> prompt (allow multiple files) ftp> ascii (transfer in ascii text mode) ftp> mget mu* (get all files whose names start with mu) ftp> bye (log off the FTP server) $
Others discussed here:
There's nothing wrong with Telnet. In fact it's far superior to SSH as a virtual terminal protocol in terms of features and extensibility, not to mention platform neutrality. Of course clear-text Telnet is insecure because passwords travel in the clear across the network, but apparently few people realize that secure Telnet clients and servers have been available for years, and these are more secure than SSH for reasons explained HERE. (If you don't bother to follow the link, the short version is manageability, especially regarding recovery from compromised keys.) Increasingly, Internet standard security methods such as Kerberos and SSL/TLS are included in standard distributions of Unix (Linux, FreeBSD, OpenBSD, AIX, Solaris, HP-UX, ...), VMS, and other operating systems, supported in their Telnet and/or FTP servers and/or clients. And of course they are also supported by C-Kermit for Unix and VMS and by Kermit 95 for Windows (which also supports SSH v1/v2).
Similarly for FTP. SCP and SFTP are not only not platform neutral, they're diversity-hostile. They transfer files only in binary mode, which mangles text files across different platforms, to the same degree the platforms' text-file record formats and character sets differ. An extreme example would be a Variable-Block format EBCDIC text file on an IBM mainframe, binary transfer of which to Unix would do you little good indeed. FTP was designed with diversity in mind and secure versions are available.
Of course SSH has its place, but you should use it with your eyes open, especially from Windows (where key files are easily stolen). SSH is best suited for trivial cross-realm applications. For example, if you have guest IDs at other sites for building an application on different platforms. Formerly Telnet and FTP would be used for this but now these paths tend to be blocked. However, even if the remote site has Kerberos service or X.509 certificates, it would be unnecessarily time-consuming to set up the cross-realm authentication and/or ticket forwarding for little one-shot jobs like this. In this case, SSH with manual password authentication is fine.
But for more serious work, especially within large organizations such as universities, corporations, laboratories, and government agencies, where your whole online identity is at stake, a manageable centralized security architecture is essential.
NOTE: "UNIX" is a general term covering the many operating systems that descended from the original Bell Labs UNIX operating system. Examples include: Linux, Mac OS X, FreeBSD, NetBSD, OpenBSD, Solaris, SunOS, AIX, HP-UX, IRIX, OPENSTEP, NeXTSTEP, System V, Tru64, OSF/1, DG/UX, Unixware, Xenix, OpenServer, BSDI/OS, Ultrix, Digital UNIX, SINIX, and many more (for a longer list, CLICK HERE).