1. 01 11月, 2000 2 次提交
  2. 27 10月, 2000 1 次提交
  3. 22 10月, 2000 2 次提交
  4. 14 10月, 2000 1 次提交
  5. 13 10月, 2000 1 次提交
    • R
      Rework the system to generate shared libraries: · a22fb399
      Richard Levitte 提交于
        - Make note of the expected extension for the shared libraries and
          if there is a need for symbolic links from for example libcrypto.so.0
          to libcrypto.so.0.9.7.  There is extended info in Configure for
          that.
      
        - Make as few rebuilds of the shared libraries as possible.
      
        - Still avoid linking the OpenSSL programs with the shared libraries.
      
        - When installing, install the shared libraries separately from the
          static ones.
      a22fb399
  6. 09 10月, 2000 2 次提交
  7. 22 9月, 2000 1 次提交
  8. 21 9月, 2000 1 次提交
  9. 19 9月, 2000 1 次提交
  10. 18 9月, 2000 2 次提交
  11. 14 9月, 2000 1 次提交
  12. 13 9月, 2000 1 次提交
  13. 12 9月, 2000 1 次提交
  14. 06 9月, 2000 2 次提交
    • B
      Changes for QNX: there is no thread support, and the previous · 36124b10
      Bodo Möller 提交于
      configuration only worked with no-asm.
      36124b10
    • D
      *BIG* verify code reorganisation. · 2f043896
      Dr. Stephen Henson 提交于
      The old code was painfully primitive and couldn't handle
      distinct certificates using the same subject name.
      
      The new code performs several tests on a candidate issuer
      certificate based on certificate extensions.
      
      It also adds several callbacks to X509_VERIFY_CTX so its
      behaviour can be customised.
      
      Unfortunately some hackery was needed to persuade X509_STORE
      to tolerate this. This should go away when X509_STORE is
      replaced, sometime...
      
      This must have broken something though :-(
      2f043896
  15. 04 9月, 2000 1 次提交
  16. 01 9月, 2000 1 次提交
  17. 17 8月, 2000 1 次提交
  18. 15 8月, 2000 1 次提交
  19. 02 8月, 2000 3 次提交
  20. 25 7月, 2000 1 次提交
  21. 21 7月, 2000 1 次提交
    • R
      Redo and enhance the support for building shared libraries. Currently · b436a982
      Richard Levitte 提交于
      there's support for building under Linux and True64 (using examples
      from the programming manuals), including versioning that is currently
      the same as OpenSSL versions but should really be a different series.
      
      With this change, it's up to the users to decide if they want shared
      libraries as well as the static ones.  This decision now has to be
      done at configuration time (well, not really, those who know what they
      do can still do it the same way as before).
      
      The OpenSSL programs (openssl and the test programs) are currently
      always linked statically, but this may change in the future in a
      configurable manner.  The necessary makefile variables to enable this
      are in place.
      
      Also note that I have done absolutely nothing about the Windows target
      to get something similar.  On the other hand, DLLs are already the
      default there, but without versioning, and I've no idea what the
      possibilities for such a thing are there...
      b436a982
  22. 21 6月, 2000 1 次提交
  23. 13 6月, 2000 1 次提交
  24. 09 6月, 2000 1 次提交
  25. 07 6月, 2000 1 次提交
  26. 06 6月, 2000 1 次提交
    • A
      · 62187daf
      Andy Polyakov 提交于
      MT-support for IRIX 6.x and Alpha-Linux
      62187daf
  27. 04 6月, 2000 2 次提交
  28. 03 6月, 2000 1 次提交
  29. 01 6月, 2000 1 次提交
    • G
      This change will cause builds (by default) to not use different STACK · e41c8d6a
      Geoff Thorpe 提交于
      structures and functions for each stack type. The previous behaviour
      can be enabled by configuring with the "-DDEBUG_SAFESTACK" option.
      This will also cause "make update" (mkdef.pl in particular) to
      update the libeay.num and ssleay.num symbol tables with the number of
      extra functions DEBUG_SAFESTACK creates.
      
      The way this change works is to accompany each DECLARE_STACK_OF()
      macro with a set of "#define"d versions of the sk_##type##_***
      functions that ensures all the existing "type-safe" stack calls are
      precompiled into the underlying stack calls. The presence or abscence
      of the DEBUG_SAFESTACK symbol controls whether this block of
      "#define"s or the DECLARE_STACK_OF() macro is taking effect. The
      block of "#define"s is in turn generated and maintained by a perl
      script (util/mkstack.pl) that encompasses the block with delimiting
      C comments. This works in a similar way to the auto-generated error
      codes and, like the other such maintenance utilities, is invoked
      by the "make update" target.
      
      A long (but mundane) commit will follow this with the results of
      "make update" - this will include all the "#define" blocks for
      each DECLARE_STACK_OF() statement, along with stripped down
      libeay.num and ssleay.num files.
      e41c8d6a
  30. 30 5月, 2000 2 次提交
  31. 25 5月, 2000 1 次提交