🚀 go-pugleaf

In article <WVENABLE.92Aug15142816@algona.stats.adelaide.edu.au> wvenable@algona.stats.adelaide.edu.au (Bill Venables) writes:

>uuencoding is not necessary for files transferred by remote ftp, so long as
>"binary" mode is set during transmission.

I would not like the lack of access to uudecode to be a problem,
so I have placed a non-uuencoded file, stat.tar.Z.crypt, in
the pub/stat directory at ftp.cis.ohio-state.edu.

>I suppose it is well known that the "crypt" facility is still an illegal
>export from the US and (in theory) should not exist on any machine outside
>the US.  So persons like me outside the US intending to get |STAT this way
>will need first to get an account somewhere inside the US, remote login to
>it, ftp it there first, decrypt it there, re-ftp it home and so on.  But if
>that's the deal, then I guess that's the deal.

crypt is based on WWII technology and does not include controlled
encryption methods.  I use crypt in the MKS toolkit, imported into
the US from Canada.  Still, if you don't have crypt, then you don't have it.

The "deal" is that I do not want |STAT placed on a bulletin board or
and ftp site without some assurance that people will abide by its restrictions
(those basically being that you can't distribute modified copies).

I am willing to send stat.tar.Z.uu (without encryption) to those who
send me the line:
	I AGREE TO ADHERE TO THE CONDITIONS OF USING |STAT.
The message would be a little over 500 Kbytes.

Some people have sent me some messages about problems compiling |STAT
on their machines.  I have made some changes in the declarations of
functions to overcome these, but if you find more, then send me a
transcript of the compiler messages and I will try to address them.
-- 
Name:  Gary Perlman               | Computer and Information Science Department
Email: perlman@cis.ohio-state.edu | Ohio State University, 228 Bolz Hall
Phone: 614-292-2566               | 2036 Neil Avenue Mall
Fax:   614-785-9837 or 292-9021   | Columbus, OH 43210-1277  USA