1. 26 9月, 2001 3 次提交
  2. 25 9月, 2001 1 次提交
  3. 14 9月, 2001 1 次提交
  4. 11 9月, 2001 1 次提交
  5. 07 9月, 2001 1 次提交
  6. 06 9月, 2001 1 次提交
  7. 05 9月, 2001 2 次提交
  8. 03 9月, 2001 1 次提交
  9. 02 9月, 2001 1 次提交
    • G
      Make the necessary changes to work with the recent "ex_data" overhaul. · 79aa04ef
      Geoff Thorpe 提交于
      See the commit log message for that for more information.
      
      NB: X509_STORE_CTX's use of "ex_data" support was actually misimplemented
      (initialisation by "memset" won't/can't/doesn't work). This fixes that but
      requires that X509_STORE_CTX_init() be able to handle errors - so its
      prototype has been changed to return 'int' rather than 'void'. All uses of
      that function throughout the source code have been tracked down and
      adjusted.
      79aa04ef
  10. 01 9月, 2001 1 次提交
  11. 27 8月, 2001 1 次提交
  12. 18 8月, 2001 1 次提交
  13. 31 7月, 2001 1 次提交
  14. 11 7月, 2001 2 次提交
  15. 24 6月, 2001 1 次提交
  16. 11 6月, 2001 1 次提交
  17. 06 6月, 2001 1 次提交
  18. 13 5月, 2001 2 次提交
  19. 07 5月, 2001 1 次提交
  20. 27 4月, 2001 3 次提交
  21. 23 4月, 2001 1 次提交
  22. 29 3月, 2001 1 次提交
  23. 21 3月, 2001 1 次提交
  24. 14 3月, 2001 1 次提交
  25. 02 3月, 2001 2 次提交
    • R
      Sort platforms lexicographically as well. Also, support more than two · c454dbcd
      Richard Levitte 提交于
      variants of a symbol.
      c454dbcd
    • R
      Introduce the possibility to access global variables through · 62dc5aad
      Richard Levitte 提交于
      functions on platform were that's the best way to handle exporting
      global variables in shared libraries.  To enable this functionality,
      one must configure with "EXPORT_VAR_AS_FN" or defined the C macro
      "OPENSSL_EXPORT_VAR_AS_FUNCTION" in crypto/opensslconf.h (the latter
      is normally done by Configure or something similar).
      
      To implement a global variable, use the macro OPENSSL_IMPLEMENT_GLOBAL
      in the source file (foo.c) like this:
      
      	OPENSSL_IMPLEMENT_GLOBAL(int,foo)=1;
      	OPENSSL_IMPLEMENT_GLOBAL(double,bar);
      
      To declare a global variable, use the macros OPENSSL_DECLARE_GLOBAL
      and OPENSSL_GLOBAL_REF in the header file (foo.h) like this:
      
      	OPENSSL_DECLARE_GLOBAL(int,foo);
      	#define foo OPENSSL_GLOBAL_REF(foo)
      	OPENSSL_DECLARE_GLOBAL(double,bar);
      	#define bar OPENSSL_GLOBAL_REF(bar)
      
      The #defines are very important, and therefore so is including the
      header file everywere where the defined globals are used.
      
      The macro OPENSSL_EXPORT_VAR_AS_FUNCTION also affects the definition
      of ASN.1 items, but that structure is a bt different.
      
      The largest change is in util/mkdef.pl which has been enhanced with
      better and easier to understand logic to choose which symbols should
      go into the Windows .def files as well as a number of fixes and code
      cleanup (among others, algorithm keywords are now sorted
      lexicographically to avoid constant rewrites).
      62dc5aad
  26. 26 2月, 2001 1 次提交
    • R
      make update · d88a26c4
      Richard Levitte 提交于
      Note that all *_it variables are suddenly non-existant according to
      libeay.num.  This is a bug that will be corrected.  Please be patient.
      d88a26c4
  27. 22 2月, 2001 1 次提交
  28. 21 2月, 2001 1 次提交
  29. 20 2月, 2001 1 次提交
    • R
      Make all configuration macros available for application by making · cf1b7d96
      Richard Levitte 提交于
      sure they are available in opensslconf.h, by giving them names starting
      with "OPENSSL_" to avoid conflicts with other packages and by making
      sure e_os2.h will cover all platform-specific cases together with
      opensslconf.h.
      
      I've checked fairly well that nothing breaks with this (apart from
      external software that will adapt if they have used something like
      NO_KRB5), but I can't guarantee it completely, so a review of this
      change would be a good thing.
      cf1b7d96
  30. 19 2月, 2001 1 次提交
  31. 29 12月, 2000 1 次提交
  32. 28 11月, 2000 1 次提交