When no SRP identity is found, no error was reported server side

[openssl.git] / INSTALL

diff --git a/INSTALL b/INSTALL
index 2fd80d821512501dfa26ee548df16683c1438e3d..8f0acf8321ce5706c34d91f8de85862ddcebf928 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -310,6 +310,13 @@
   no-err
                    Don't compile in any error strings.
 
   no-err
                    Don't compile in any error strings.
 

+  enable-external-tests
+                   Enable building of integration with external test suites.
+                   This is a developer option and may not work on all platforms.
+                   The only supported external test suite at the current time is
+                   the BoringSSL test suite. See the file test/README.external
+                   for further details.
+

   no-filenames
                    Don't compile in filename and line number information (e.g.
                    for errors and memory allocation).
   no-filenames
                    Don't compile in filename and line number information (e.g.
                    for errors and memory allocation).


@@ -457,6 +464,12 @@
                    specific configuration, e.g. "-m32" to build x86 code on
                    an x64 system.
 
                    specific configuration, e.g. "-m32" to build x86 code on
                    an x64 system.
 

+  enable-tls1_3
+                   TODO(TLS1.3): Make this enabled by default
+                   Build support for TLS1.3. Note: This is a WIP feature and
+                   does not currently interoperate with other TLS1.3
+                   implementations! Use with caution!!
+

   no-<prot>
                    Don't build support for negotiating the specified SSL/TLS
                    protocol (one of ssl, ssl3, tls, tls1, tls1_1, tls1_2, dtls,
   no-<prot>
                    Don't build support for negotiating the specified SSL/TLS
                    protocol (one of ssl, ssl3, tls, tls1, tls1_1, tls1_2, dtls,


@@ -474,12 +487,12 @@
 
   enable-<alg>
                    Build with support for the specified algorithm, where <alg>
 
   enable-<alg>
                    Build with support for the specified algorithm, where <alg>

-                   is one of: md2, mdc2, or rc5.
+                   is one of: md2 or rc5.

 
   no-<alg>
                    Build without support for the specified algorithm, where
                    <alg> is one of: bf, blake2, camellia, cast, chacha, cmac,
 
   no-<alg>
                    Build without support for the specified algorithm, where
                    <alg> is one of: bf, blake2, camellia, cast, chacha, cmac,

-                   des, dh, dsa, ecdh, ecdsa, idea, md4, ocb, poly1305,
+                   des, dh, dsa, ecdh, ecdsa, idea, md4, mdc2, ocb, poly1305,

                    rc2, rc4, rmd160, scrypt, seed or whirlpool. The "ripemd"
                    algorithm is deprecated and if used is synonymous with rmd160.
 
                    rc2, rc4, rmd160, scrypt, seed or whirlpool. The "ripemd"
                    algorithm is deprecated and if used is synonymous with rmd160.
 


@@ -601,17 +614,14 @@
      ("openssl"). The libraries will be built in the top-level directory,
      and the binary will be in the "apps" subdirectory.
 
      ("openssl"). The libraries will be built in the top-level directory,
      and the binary will be in the "apps" subdirectory.
 

-     If the build fails, look at the output.  There may be reasons for
-     the failure that aren't problems in OpenSSL itself (like missing
-     standard headers).  If you are having problems you can get help by
-     sending an email to the openssl-users email list (see
-     https://www.openssl.org/community/mailinglists.html for details). If it
-     is a bug with OpenSSL itself, please report the problem to
-     <rt@openssl.org> (note that your message will be recorded in the request
-     tracker publicly readable at
-     https://www.openssl.org/community/index.html#bugs and will be
-     forwarded to a public mailing list). Please check out the request
-     tracker. Maybe the bug was already reported or has already been
+     If the build fails, look at the output.  There may be reasons
+     for the failure that aren't problems in OpenSSL itself (like
+     missing standard headers).  If you are having problems you can
+     get help by sending an email to the openssl-users email list (see
+     https://www.openssl.org/community/mailinglists.html for details). If
+     it is a bug with OpenSSL itself, please open an issue on GitHub, at
+     https://github.com/openssl/openssl/issues. Please review the existing
+     ones first; maybe the bug was already reported or has already been

      fixed.
 
      (If you encounter assembler error messages, try the "no-asm"
      fixed.
 
      (If you encounter assembler error messages, try the "no-asm"


@@ -963,7 +973,7 @@
  and libssl-1_1-x64.dll for 64-bit x86_64 Windows, and libcrypto-1_1-ia64.dll
  and libssl-1_1-ia64.dll for IA64 Windows.  With MSVC, the import libraries
  are named libcrypto.lib and libssl.lib, while with MingW, they are named
  and libssl-1_1-x64.dll for 64-bit x86_64 Windows, and libcrypto-1_1-ia64.dll
  and libssl-1_1-ia64.dll for IA64 Windows.  With MSVC, the import libraries
  are named libcrypto.lib and libssl.lib, while with MingW, they are named

- libcrypto.dll.a and libddl.dll.a.
+ libcrypto.dll.a and libssl.dll.a.

 
  On VMS, shareable images (VMS speak for shared libraries) are named
  ossl$libcrypto0101_shr.exe and ossl$libssl0101_shr.exe.  However, when
 
  On VMS, shareable images (VMS speak for shared libraries) are named
  ossl$libcrypto0101_shr.exe and ossl$libssl0101_shr.exe.  However, when