Subject: Pine enhancement requests

From: Andrew Douglas Inman <[email-masked]>
Date: Wed, 6 Apr 1994 16:25:13 -0400 (EDT)

The three addition's I'd like to see in pine are as follows:

The ability to add additional header lines in when sending mail.

The ability to change your default editor and use it for the headers and 
everything.

Built-in pgp support,

I'm sure these aren't as popular as other things, but I thought I'd put 
in my two cents worth.

       -- Andrew ([email-masked])

---

From: David L Miller <[email-masked]>
Date: Wed, 6 Apr 1994 14:18:43 -0700 (PDT)

Andrew,

The next release of Pine will allow you to configure additional headers 
in your .pinerc file.  

Allowing the alternate-editor to manipulate the headers is a tough problem
that we are deferring for now.  We are improving the way editing the body is
handled though. 

There are some legal and political roadblocks to be passed before we would be
comfortable adding PGP support.  

Thanks for the suggestions!

--DLM

|\ |  |\/|  David L. Miller    [email-masked]  (206) 685-6240
|/ |_ |  |  Software Engineer, Pine Development Team   (206) 685-4045 (FAX)
University of Washington, Networks & Distributed Computing, JE-20
4545 15th Ave NE, Seattle WA 98105, USA

---

From: "Andrew B. Sweger" <[email-masked]>
Date: Wed, 6 Apr 1994 15:06:39 -0700 (PDT)

> Andrew,
	[items deleted] 
> comfortable adding PGP support.  
	[items deleted]

	Perhaps a future version of pine could have appropriate locations
for hooks to various privacy packages to be added by the installer (but
not provided in the distribution). Maybe user installable menu commands
(e.g., Sign Message (specify MIME part number), Encrypt MIME part) would
be possible for the hacker (site implementor?). This doesn't solve all the
legal or political roadblocks, but does put some distance from the problem
and gives some folks a solution.  The hooks don't have to be strictly for
PGP, any package would apply. (IMHO, ignorant as it is) -Andy

-- 
  /  Andrew B. Sweger                      [email-masked]
 //  Computer Support Manager              [email-masked]
 \\  Department of Family Medicine, HQ-30  (206) 543-2461 (Office)
 //  UNIVERSITY OF WASHINGTON              (206) 685-4337 (Voice Mail)
 /   Seattle, WA 98195                     (206) 685-0610 (FAX)
------------------------------------------------------------------------------
The great thing about multitasking is that several things can go wrong at once.
==============================================================================

---

From: Kevin Pinto <[email-masked]>
Date: Wed, 06 Apr 1994 15:18:13 -0700 (MST)

Hi

I use multiple incoming folders, (with delivery to them via procmail) and 
they are listed in my .pinerc

I find though, that they're displayed in alphabetical order.  While this 
may be neat and tidy, the high volume folders are at the end, meaning 
that I have to TAB through empty folders before reaching the ones I want.

Are there any plans to change this?

Regards,
Kevin

-----------------------------------------------------------------------------
Kevin Pinto, Chem Engg, ASU, Tempe, AZ                 <[email-masked]>
My mailer understands MIME
"Beware of reading health books; you may die of a misprint" - Mark Twain
"An armed society is a polite society" - Beyond This Horizon, Robert Heinlein

---

From: David L Miller <[email-masked]>
Date: Wed, 6 Apr 1994 15:41:17 -0700 (PDT)

Kevin,

The next release of Pine will display the incoming folders in .pinerc 
order.

Thanks for the request!

--DLM

---

From: David L Miller <[email-masked]>
Date: Wed, 6 Apr 1994 16:09:08 -0700 (PDT)

Andrew,

That approach is a possibility, but I think of it as hack to use as a 
last resort in case we get desparate.  That is unless someone comes up 
with a good generic API that everyone can use ;)

Thanks for the suggestion!

--DLM

---

From: "Richard C. Gaine" <[email-masked]>
Date: Thu, 7 Apr 1994 10:18:38 -0400 (EDT)

Hi,
	When is the next release of Pine due out?

---

From: David L Miller <[email-masked]>
Date: Thu, 7 Apr 1994 09:37:10 -0700 (PDT)

We are hoping for a beta release sometime this spring...

---

From: Bruce Mahfood <[email-masked]>
Date: Tue, 12 Apr 1994 11:39:33 -0400 (EDT)

This is a great idea.  Then, also, if any of those hackers do come up 
with some good code that they would be willing to share, they could 
submit that to the pine crew as part of the next release.  That way, pine 
people don't have to do it all...

****************************************************************************
!  Bruce Mahfood   [email-masked]   !                                       !
!  Cambridge Technology Partners   !  "It amazes me the will of instinct"  !
!  304 Vassar St.                  !              Nirvana                  !
!  Cambridge, MA 02139             !                                       !
****************************************************************************

---

From: David L Miller <[email-masked]>
Date: Tue, 12 Apr 1994 08:51:39 -0700 (PDT)

Bruce,

Unfortunately the contributed code has to get past the same roadblocks as any
code we would write.  We have already been offered a couple PGP patches for
Pine, but we cannot do anything with them until the legal dust settles :(

--DLM

---

From: Ed Greshko <[email-masked]>
Date: Wed, 13 Apr 1994 08:14:37 +0800 (TPE)

> Pine, but we cannot do anything with them until the legal dust settles :(

	While a PGP specific patch may suffer from legal problems the original
request suggested a "generic" hook so that people could plug in their own
privacy package.  Do you see any problems with that approach?

						Ed

Edward M. Greshko			Control Data Taiwan
Voice: +886-2-715-2222 x287		6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197			Taipei, Taiwan R.O.C

---

From: Goran Svensson <[email-masked]>
Date: Wed, 13 Apr 1994 08:36:55 +0200 (DFT)

-----BEGIN PGP SIGNED MESSAGE-----

> > Pine, but we cannot do anything with them until the legal dust settles :(

PGP is using RSA protected by a US patent, therefore possibly breaking US 
patent laws. Also, PGP can not be exported outside US.
*BUT*, PGP is legally sold under the name ViaCrypt, under legal license 
terms. See alt.security.pgp .

Therefore, calling PGP from inside pine can not in my opinion break any law.
Inside US, it is a permitted when bought as ViaCrypt, and outside US there
is not any law against it.

> FAX  : +886-2-712-9197			Taipei, Taiwan R.O.C

*******************************************************************************
* Goran Svensson                     * Believe it or not, this is my opinion. *
* BTJ System AB, Lund, Sweden        * I reserve the right to change it,      *
* Email: [email-masked]                * doubt it or deny it at any time.       *
* Phone: +46 46 18 00 00             ******************************************
* Fax: +46 46 18 03 33               * Snail: Box 4066, S-227 21 Lund, Sweden *
*******************************************************************************
*   Believe nothing, no matter where you read it, or who said it, no matter   *
*   if I have said it, unless it agrees with your own reason and your own     *
*   common sense."                                                            *
*                     --Buddha                                                *
*******************************************************************************

---

From: root <[email-masked]>
Date: Thu, 14 Apr 1994 22:21:23 +0000

> Thanks for the suggestion!

Does that really apply if the contributed code is just a patch which 
allows an external program called 'pgp' to be called? Or a program which 
is called 'tom', maybe, which just might happen to be 'pgp'? How could 
there be any legal problem with that?

There is just such a patch floating around. And there seems to be 
considerable demand.

Charlie Brady * (W) [email-masked] * (H) [email-masked]
"Make it as simple as possible - | Tel: (02) 413 6838 ____Telectronics__| /\__
  but no simpler"   Einstein, A  | Fax: (02) 413 6868 Pacing Systems    \/

---

From: Ian Dunkin <[email-masked]>
Date: Fri, 15 Apr 1994 18:11:11 +0100 (BST)

> comfortable adding PGP support.  

Might RSA's recent announcement (below) that their RIPEM/SIG digital
signature software is now free and exportable come in somewhere here, in
the area of support for such signatures in Pine?  I gather this is
possible because they got a "commodities jurisdiction" ruling that the
software falls under the Commerce Department's jurisdiction as opposed
to the State Department and thus allows it to be freely and legally
exported. 

    ?I.

--
Ian Dunkin <[email-masked]>
--

                            o /
-----------------------------x------------------------------------------
                            O \

>From [email-masked] Fri Apr 15 18:01:01 1994
Date: Fri, 25 Mar 94 12:00:52 PST
From: Jim Bidzos <[email-masked]>
To: [email-masked]
Subject: RSAREF/RIPEM Free and Legal Worldwide

More info...

>From [email-masked] Fri Mar 25 11:59:34 1994
X-Sender: [email-masked]
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Mailer: Eudora 2.0.2
Organization: Consensus Development Corporation, San Francisco, CA USA
Date: Wed, 23 Mar 1994 14:53:10 -0800
To: [email-masked], [email-masked], [email-masked]
From: Christopher Allen <[email-masked]>
Subject: ARTICLE - Two Updates Make for Digital Signatures in Email
Sender: [email-masked]

-----BEGIN PRIVACY-ENHANCED MESSAGE-----
Proc-Type: 4,MIC-CLEAR
Content-Domain: RFC822
Originator-Certificate:
 MIICETCCAaYCBQJBAADUMA0GCSqGSIb3DQEBAgUAMGMxCzAJBgNVBAYTAlVTMSAw
 HgYDVQQKExdSU0EgRGF0YSBTZWN1cml0eSwgSW5jLjEyMDAGA1UECxMpVW5hZmZp
 bGlhdGVkIFVzZXIgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwHhcNOTMxMDI2MDAw
 MDAwWhcNOTUxMDI2MjM1OTU5WjCBqjELMAkGA1UEBhMCVVMxEzARBgNVBBETCjk0
 MTE0LTM2MTUxCzAJBgNVBAgTAkNBMRYwFAYDVQQHEw1TYW4gRnJhbmNpc2NvMUUw
 QwYDVQQJFDxjL28gQ29uc2Vuc3VzIERldmVsb3BtZW50IENvcnBvcmF0aW9uLCA0
 MTA0LTI0dGggU3RyZWV0IKY0MTkxGjAYBgNVBAMTEUNocmlzdG9waGVyIEFsbGVu
 MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBAMDg2GDo+1J5OQ+Sx6Ub3WkKzJkBV1f+
 uognXb5tTNOdskyKKmMpNivX3yNW9yLNxdaMSU7/s8Nq5Oh3Y7KMunUCAwEAATAN
 BgkqhkiG9w0BAQIFAANWAAEnzrJ1IFNscUI4zJl7HjZIw4rR2Zmh7nJ0qVH55X72
 DU8VP/TBdiEWbhfM1qMthQqmnTNYZ9aq7J1d54nRMbk0ccqSapmqknaKiWqdCXBj
 Qcxg88p=
Issuer-Certificate:
 MIIB/jCCAWsCBQIFAAABMA0GCSqGSIb3DQEBAgUAMFwxCzAJBgNVBAYTAlVTMSAw
 HgYDVQQKExdSU0EgRGF0YSBTZWN1cml0eSwgSW5jLjErMCkGA1UECxMiQ29tbWVy
 Y2lhbCBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw05MzA1MDEwMDAwMDBaFw05
 ODA0MzAyMzU5NTlaMGMxCzAJBgNVBAYTAlVTMSAwHgYDVQQKExdSU0EgRGF0YSBT
 ZWN1cml0eSwgSW5jLjEyMDAGA1UECxMpVW5hZmZpbGlhdGVkIFVzZXIgQ2VydGlm
 aWNhdGlvbiBBdXRob3JpdHkwcDANBgkqhkiG9w0BAQEFAANfADBcAlUxe5CmA5dy
 igi8ZWJpGJdctHi5wvnIVcG9aupi7+ym5hDyFtVLEeJy5U31xIHz/RSoRJvy0RiY
 LtSUOZWWlHol6aEzss1lEknAZNX1aluc+ia7NuvxAgMBAAEwDQYJKoZIhvcNAQEC
 BQADfgBe/pia8Oo46rbZlEZE5S0JDsrqWRS5v2ia0D55lJHQqr5vLY0pJy4sSbcp
 0r7ZihMMEEO4o8Mu5ZjM8F1ZfEXPy0mWaHPoVxvb13sXgo17Q9m2U58hvjI72U0m
 nyB7fXhsjlnFSm8PN0zaTx6RRv8dxvyC42V2mPz6xciQcw==
MIC-Info: RSA-MD5,RSA,
 BVNiXNeTZzv5ChVt/OzLHOvgQ0XbSIW5GsUV/Da58fSVFcxc+OF2R6MMH3NxcWPu
 tlpZNMVi51vRzw0pLH2psg==

Date: Wed, 23 Mar 1994 14:41:00 -0800
Subject: ARTICLE - Two Updates Make for Digital Signatures in Email
From: Christopher Allen <[email-masked]>
Reply-To: Christopher Allen <[email-masked]>
Originator: Christopher Allen <[email-masked]>
Organization: Consensus Development Corporation, San Francisco, CA USA
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: [email-masked]
X-Last-Updated: 1994/03/23
X-Text-Source:
ftp://netcom7.netcom.com/pub/consensus/text/Two_Updates_Dig_Sig.txt
X-HTML-Source:
ftp://netcom7.netcom.com/pub/consensus/www/Two_Updates_Dig_Sig.html
Summary: This article is about two recent software updates, RIPEM 1.2 and
  RSAREF 2.0, which are significanct to the progress of using digital
  signatures in electronic mail.
Keywords: article, christopher allen, consensus development, ripem,
  ripem/sig, rsaref, digital, signature, electronic, mail, email,
  security, privacy, privacy enhanced mail, pem, export, decryption
  encryption, cryptography, authentication, rsa data security, pgp,
  pretty good privacy, software, license, patent

TWO UPDATES MAKE FOR DIGITAL SIGNATURES IN EMAIL
================================================
by Christopher Allen <[email-masked]>
Copyright (c)1994 by Consensus Development Corporation--All Rights
Reserved. See the end of this article for the full copyright notice.

DIGITAL SIGNATURES
- ------------------
One of the real up-and-coming uses of encryption technology is for
applying digital ``signatures'' to various electronic documents. Such
signatures are not forgeable and guarantee that a document originates
with its author. If Dartmouth College had such a system in place
recently, a message impersonating a faculty member announcing the
cancellation of an exam might have been avoided. Digital signatures can
also be used to detect viruses before infected files execute.

Up to now, however, digitally signing documents has not been an easy
task. The first hurdle has been an inability to export the technology
overseas, making it virtually impossible to standardize on a signature
method. Secondly, it has been difficult to license the technology
patents involved.

The use of a freeware software utility called Pretty Good Privacy (PGP)
has caused some difficulties as well. Since PGP has already found its
way overseas and has gained some popularity, in particular because US
digital signature software has not been easily exportable. In the United
States, many organizations are reluctant to use PGP because of its
questionable patent status. In addition, its author, Phil Zimmermann, is
under investigation for possible export violations. These problems have
kept organizations from adopting PGP as a standard.

Two recent announcements have significantly changed things.

The first announcement is the release of two new versions of RIPEM, one
called RIPEM, the other called RIPEM/SIG. RIPEM is a free version of the
Internet Privacy Enhanced Mail (PEM) standard implemented by Mark
Riordan of Michigan State University. RIPEM/SIG is a subset of RIPEM
that allows users to digitally sign their e-mail documents but does not
allow encryption or decryption.

What is significant about this announcement is that Riordan--in
cooperation with RSA Data Security, Inc--has received a ``commodities
jurisdiction'' ruling which allows free and legal export of
non-encrypting RIPEM/SIG outside of the US. This means both US and
overseas users can now standardize on a single set of software, instead
of only working with RIPEM inside the US and PGP outside.

This release also addresses some of the complaints of PGP users: both
RIPEM and RIPEM/SIG support a non-hierarchical trust model similar to
PGP, and for US users the non-exportable version of RIPEM provides full
triple-DES privacy. Even though the triple-DES RIPEM may not be
exportable, Riordan is working with authors of independently developed
PEM applications in other countries with the goal of 100%
interoperability in a version 2.0 of RIPEM. Until that time, since
RIPEM/SIG is free and exportable, users could send a non-US or Canadian
user both RIPEM/SIG and the message to be authenticated.

The second announcement is from RSA Data Security, Inc. for the 2.0
version of RSAREF. RSAREF is a source code cryptographic toolkit
designed specifically for writing PEM applications as well other
fundamental cryptographic and digital signature tools. In fact,
RIPEM is based on the RSAREF source code.

What is most significant about this new RSAREF is that RSA Data Security
has changed its license to make RSAREF much more accessible to both
corporations and commercial and non-commercial developers. Freeware
products (i.e., software where no fee other than media or bandwidth cost
is requested) can use the RSAREF toolkit provided that the public has
access to the product's source code.

Though a new license agreement has not been finalized, I've been told by
RSA that they will grant a royalty-free license for shareware products
for up to $10,000 worth of gross annual sales if the shareware source
code is available and the developers do not charge more than $50 a
copy.

Even if you are a commercial developer, I know from personal experience
that RSA can be quite reasonable about licensing. They want this base
level of technology adopted as widely as possible--just make RSA a
reasonable offer and I think they'll take it.

RIPEM and RIPEM/SIG are also beneficiaries of this new RSAREF license,
which means that US companies can have privacy and authentication free
of hassles from patent holders and export cops.

MORE ON RIPEM/SIG
- -----------------
The press release on RIPEM/SIG from Mark Riordan <[email-masked]>
is at:

        ftp://ripem.msu.edu/pub/crypt/ripem/ripemsig/posting

If you are a US or Canadian citizen, you can request an account for
access to the full non-exportable RIPEM. Information on how to get
access is at:

        ftp://guest.mu5k2d55:@ripem.msu.edu//pub/crypt/GETTING_ACCESS

The binary files for the exportable RIPEM/SIG can be found in the
directory:

        ftp://ripem.msu.edu/pub/crypt/ripem/ripemsig/binaries/

RSAREF/SIG Files available today are:

        ftp://ripem.msu.edu/pub/crypt/ripem/ripemsig/binaries/
        ripemsig-68030-macintosh-commandline-1.2a.sit.hqx

        ftp://ripem.msu.edu/pub/crypt/ripem/ripemsig/binaries/
        ripemsig-80x86-dos-vanilla-1.2a.exe

        ftp://ripem.msu.edu/pub/crypt/ripem/ripemsig/binaries/
        ripemsig-hppa-hpux9.01-1.2a

        ftp://ripem.msu.edu/pub/crypt/ripem/ripemsig/binaries/
        ripemsig-ibm-rs6000-aix3.2-1.2a

        ftp://ripem.msu.edu/pub/crypt/ripem/ripemsig/binaries/
        ripemsig-sparc-sunos4.1.1-1.2a

There does not seem to be separate documentation for RIPEM/SIG yet, so
I guess you have to use the documentation for RIPEM 1.2a:

        ftp://ripem.msu.edu/pub/crypt/ripem/ripem.man
        ftp://ripem.msu.edu/pub/crypt/ripem/ripemusr.doc
        ftp://ripem.msu.edu/pub/crypt/ripem/ripemusr.txt

A current list of RIPEM public keys is at:

        ftp://ripem.msu.edu/pub/crypt/ripem/pubkeys.txt

There is an electronic-mail users group list PEM-DEV for discussions
related to the development and deployment of Privacy Enhanced Mail (PEM)
systems. Contributions to the list should be sent to
[email-masked]''. Administrivia, e.g., additions to or deletions from
the list should be sent to [email-masked]''.

The Internet Multicasting Service <[email-masked]> is now beginning to
stamp all of their text files with RSA/RIPEM digital signatures.  You
can find their public key through a finger request to town.hall.org. For
examples of stamped files, look at:

    ftp://town.hall.org/edgar/docs/

MORE ON RSAREF 2.0
- ------------------
Remember, even though you can use RSAREF to create exportable,
non-encryption based digital signature software, the source code to
RSAREF is not exportable itself, as it can do encryption. It is only
available to US and Canadian citizens.

The press release on RSAREF from Jim Bidzos <[email-masked]> is
at:

        ftp://rsa.com//pub/RIPEM_SIG_announce.txt

Information on what RSAREF is all about and what are the license terms
are located at:

        ftp://rsa.com/rsaref/info.reply
        ftp://rsa.com/rsaref/license.txt

To get access to a time dependent directory (it changes every few
minutes) you will need to read the document:

        ftp://rsa.com/rsaref/README

If you agree to it's terms, take the directory mentioned there and
substitute it for the checksum in the directory ``U.S.-only 7c04e6''.

The compressed tar archive of RSAREF is at (remember to change the time
dependent directory!):

        ftp://rsa.com/rsaref/dist/U.S.-only-7c04e6/rsaref.tar.Z

The ZIP archive of RSAREF is at (remember to change the time dependent
directory!):

        ftp://rsa.com/rsaref/dist/U.S.-only-7c04e6/rsaref.zip

You can also get the RSAREF via email by reading the RSAREF license
agreement and sending the following message to
<[email-masked]> (If your electronic mail address is
located in Canada, please also send RSA your full name and mailing
address; they'll need it to complete a Department of State export
declaration):

     I acknowledge that I have read the RSAREF Program License
     Agreement and understand and agree to be bound by its terms and
     conditions, including without limitation its restrictions on
     foreign reshipment of the Program and information related to the
     Program. The electronic mail address to which I am requesting
     that the program be transmitted is located in the United States
     of America or Canada and I am an United States citizen, a Canadian
     citizen, or a permanent resident of the United States. The RSAREF
     Program License Agreement is the complete and exclusive agreement
     between RSA Laboratories and me relating to the Program, and
     supersedes any proposal or prior agreement, oral or written, and
     any other communications between RSA Laboratories and me relating
     to the Program.

RSA Laboratories maintains an electronic-mail users group
<[email-masked]> for discussions on RSAREF applications, bug
fixes, etc. To join the users group, send electronic mail to
<[email-masked]>.

AUTHOR'S BIOGRAPHY
- ------------------
Christopher Allen is president of Consensus Development Corporation, a
microcomputer software development & consulting firm specializing in
groupware (defined as software to support collaboration and intentional
group processes), including such related areas as hypertext, online
documentation, document architecture, electronic publishing, group
knowledge-base support tools, and creation and management of shared
collaborative spaces.

Christopher has been active in a number of other computer industry areas.
He runs the Mac Developers Forum and Newton Development SIG on America
Online, and a Mosaic/World-Wide-Web area on groupware and collaboration.
Christopher has written for a number of industry books and publications,
including MacWorld and the Macintosh Bible. He has been moderator and
speaker at MacWorld Expo's and Mactivity's groupware sessions, and
speaks as a panelist on the subject of Macintosh groupware at other
industry conferences. He was chairman of MacHack '93, a conference for
Macintosh programming gurus, is on the MacHack Planning Board, and is a
senior associate at the Foresight Institute.

COPYRIGHT NOTICE
- ----------------
This article was written by Christopher Allen <[email-masked]> and
is Copyright (c)1994 by Consensus Development Corporation--All Rights
Reserved.

This article, in whole or in part, may be used and shared in accordance
the fair-use provisions of international copyright law:

        You may print or reproduce this article for non-commercial,
        personal, or educational purposes only, provided that the
        article is not modified, and that the copyright notice and
        this notice appear in all copies;

        You may quote, mention, cite, refer to, point, or describe this
        article in books, products, online services, or other media--
        but you may not reproduce in whole or in part without
        permission.

In addition, Consensus Development Corporation grants you permission to
redistribute this article in electronic form, provided that you first
notify Consensus Development and that you receive no fees, in excess of
of normal online charges, for access to this article.

Archiving, redistribution, republication, or derivation of this article
on other terms, in any medium, including but not limited to electronic,
CD-ROM, database, or publication in print, requires the explicit
written or digitally signed consent from Consensus Development
Corporation.

These requirements are not meant to be restrictive--we are quite willing
to make our articles available even for commercial use, provided that
permission is requested.

If you have any questions about these terms, or would like information
about licensing rights from Consensus Development Corporation, please
contact us via telephone 415/647-6383, or email Christopher Allen
<[email-masked]>.

- ------------------------------------------------------------------------
..Christopher Allen                  Consensus Development Corporation..
..<[email-masked]>                         4104-24th Street #419..
..                                        San Francisco, CA 94114-3615..
..                                        o415/647-6383  f415/647-6384..
..Mosaic/World-Wide-Web Front Door:                                   ..
..ftp://netcom7.netcom.com/pub/consensus/www/ConsensusFrontDoor.html  ..
-----END PRIVACY-ENHANCED MESSAGE-----
Created with RIPEM Mac 0.8.5 b2

---

From: David L Miller <[email-masked]>
Date: Mon, 18 Apr 1994 16:28:18 -0700 (PDT)

Well, it's a start.  Unfortunately it appears to only be available for export
in binary form on a few platforms.  Where does that leave our users of
Convex, Linux and 25 or so other platforms that binaries are not available
for?