misspellings fixes by https://github.com/vlajos/misspell_fixer

  *) New option -sigopt to dgst utility. Update dgst to use

     EVP_Digest{Sign,Verify}*. These two changes make it possible to use

     alternative signing paramaters such as X9.31 or PSS in the dgst 

     alternative signing parameters such as X9.31 or PSS in the dgst 

     utility.

     [Steve Henson]

  *) Fix ssl/s3_enc.c, ssl/t1_enc.c and ssl/s3_pkt.c so that we don't

     reveal whether illegal block cipher padding was found or a MAC

     verification error occured.  (Neither SSLerr() codes nor alerts

     verification error occurred.  (Neither SSLerr() codes nor alerts

     are directly visible to potential attackers, but the information

     may leak via logfiles.)

  *) Bugfix: ssl23_get_client_hello did not work properly when called in

     state SSL23_ST_SR_CLNT_HELLO_B, i.e. when the first 7 bytes of

     a SSLv2-compatible client hello for SSLv3 or TLSv1 could be read,

     but a retry condition occured while trying to read the rest.

     but a retry condition occurred while trying to read the rest.

     [Bodo Moeller]

  *) The PKCS7_ENC_CONTENT_new() function was setting the content type as

     other platforms details on the command line without having to patch the

     Configure script everytime: One now can use ``perl Configure

     <id>:<details>'', i.e. platform ids are allowed to have details appended

     to them (seperated by colons). This is treated as there would be a static

     to them (separated by colons). This is treated as there would be a static

     pre-configured entry in Configure's %table under key <id> with value

     <details> and ``perl Configure <id>'' is called.  So, when you want to

     perform a quick test-compile under FreeBSD 3.1 with pgcc and without

7-Jan-98

    - Finally reworked the cipher string to ciphers again, so it

      works correctly

    - All the app_data stuff is now ex_data with funcion calls to access.

    - All the app_data stuff is now ex_data with function calls to access.

      The index is supplied by a function and 'methods' can be setup

      for the types that are called on XXX_new/XXX_free.  This lets

      applications get notified on creation and destruction.  Some of

	# aes-ctr.o is not a real file, only indication that assembler

	# module implements AES_ctr32_encrypt...

	$cflags.=" -DAES_CTR_ASM" if ($aes_obj =~ s/\s*aes\-ctr\.o//);

	# aes-xts.o indicates presense of AES_xts_[en|de]crypt...

	# aes-xts.o indicates presence of AES_xts_[en|de]crypt...

	$cflags.=" -DAES_XTS_ASM" if ($aes_obj =~ s/\s*aes\-xts\.o//);

	$aes_obj =~ s/\s*(vpaes|aesni)\-x86\.o//g if ($no_sse2);

	$aes_obj =~ s/\s*(vp|bs)aes-\w*\.o//g if ($fipscanisterinternal eq "y");

If the test program in question fails withs SIGILL, Illegal Instruction

exception, then you more than likely to run SSE2-capable CPU, such as

Intel P4, under control of kernel which does not support SSE2

instruction extentions. See accompanying INSTALL file and

instruction extensions. See accompanying INSTALL file and

OPENSSL_ia32cap(3) documentation page for further information.

* Why does compiler fail to compile sha512.c?

                compiler flags for any other CPU specific configuration,

                e.g. "-m32" to build x86 code on an x64 system.

  no-sse2	Exclude SSE2 code pathes. Normally SSE2 extention is

  no-sse2	Exclude SSE2 code pathes. Normally SSE2 extension is

		detected at run-time, but the decision whether or not the

		machine code will be executed is taken solely on CPU

		capability vector. This means that if you happen to run OS