doesn't have a default value like the "-config" options of other
openssl subprograms.

file name for 'ca' to come from the environment.

Submitted by:
Reviewed by:
PR:

Submitted by:
Reviewed by:
PR:

this stuff.

according to the sources.... found by Steffen Dettmer <steffen@tfh-berlin.de>.

shouldn't again start with thousend little text files or we quickly come back
to the old SSLeay days ;-)

make 'req' check the config file syntax before it adds extensions. Added
info in the documentation as well.

by BUF_MEM_strdup(). Added text documentation to the BUF_MEM stuff.

doc/openssl_button.{gif,html} which is similar in style to the old SSLeay
button and can be used by applications based on OpenSSL to show the
relationship to the OpenSSL project.

PS: This beast caused me three hours to create, because
    of the size I had to hand-paint the 7pt fonts in Photoshop.

because they are useful for the DSA situation and should be recognized by the
users. Thanks to Steve for the original hint.

info will come later...

Feel free to reformat and tidy this up...

1. merge various obsolete readme texts into doc/ssleay.txt
   where we collect the old documents and readme texts.

2. remove the first part of files where I'm already sure that we no longer need
   them because of three reasons: either they are just temporary files which
   were left by Eric or they are preserved original files where I've verified
   that the diff is also available in the CVS via "cvs diff -rSSLeay_0_8_1b"
   or they were renamed (as it was definitely the case for the crypto/md/
   stuff).

We've still a horrible mess under crypto/bn/asm/.  There for a lot of files
I'm sure whether we need them or not. So, when someone knows it better, feel
free to cleanup there.

And the first steps to descriptions in prosa.

is a pain to do, because of the various macro definitions which I had to
expand manually to get their prototype :-(

What's now needed is a volunteer who wants to write down one or two sentences
per API function to document it a little bit...

together in a ssleay.txt file.

They are written in Perl's POD format for two reasons: First Perl is already
needed for SSLeay and second, POD is easy to write and maintain _AND_ created
nice looking NRoff manpages.

The idea is to have three manual pages:

  openssl(1) ... The manpage for the `openssl' program (formerly ssleay)
  crypto(3) .... The manpage for crypto.h/libcrypto.a
  ssl(3) ....... The manpage for ssl.h/libssl.a

The openssl(1) should be very similar to cvs(1), i.e.  it should document all
commands in a compact way.  And I've even created the first cut for an
overview of all 243 functions of the SSL API for ssl.pod. More to come...