both a patch level and a beta status.  IMHO, it also makes more sense
to have beta status be part of the development status than to have it
be an alternate name for patch levels under special conditions.

This may still contain a few errors from the old documentation,
but most of it should make sense.

See http://www.pdc.kth.se/kth-krb/

Their solution for CRAY is somewhat awkward.
I'll assume that a "short" is 32 bits on CRAY to avoid the
#ifdef _CRAY
    typedef struct {
        unsigned int a:32;
        unsigned int b:32;
    } XXX;
#else
    typedef DES_LONG XXX;
#endif

openssl.c: make damn sure e_os.h knows about OPENSSL_C

(Should we point to snapshots, or directly give the one-line patch?)

I hope all memory leaks that may occur here have already been tracked down.

that is actually used (even though it may not appear so at first
sight).

This was meant for building individual ciphers separately;
but nothing of this is maintained, it does not work
because we rely on central configuration by the Configure
utility with <openssl/opensslconf.h> etc., so the files
are only wasting space and time.

lib$-functions and sys$-functions.

in addition to the crypto library.