1. 12 1月, 2015 1 次提交
  2. 31 12月, 2014 1 次提交
  3. 23 12月, 2014 1 次提交
  4. 22 12月, 2014 1 次提交
  5. 20 12月, 2014 1 次提交
  6. 19 12月, 2014 1 次提交
  7. 18 12月, 2014 1 次提交
  8. 25 9月, 2014 1 次提交
  9. 09 8月, 2014 2 次提交
  10. 20 12月, 2011 1 次提交
    • D
      PR: 2563 · ad89bf78
      Dr. Stephen Henson 提交于
      Submitted by: Paul Green <Paul.Green@stratus.com>
      Reviewed by: steve
      
      Improved PRNG seeding for VOS.
      ad89bf78
  11. 27 7月, 2010 1 次提交
  12. 24 9月, 2009 1 次提交
  13. 20 4月, 2009 1 次提交
  14. 21 5月, 2007 1 次提交
  15. 12 4月, 2006 1 次提交
    • U
      Add BeOS support. · 4700aea9
      Ulf Möller 提交于
      PR: 1312
      Submitted by: Oliver Tappe <zooey@hirschkaefer.de>
      Reviewed by: Ulf Moeller
      4700aea9
  16. 19 12月, 2005 1 次提交
  17. 03 8月, 2005 1 次提交
  18. 14 4月, 2005 1 次提交
  19. 19 12月, 2004 1 次提交
  20. 27 7月, 2004 1 次提交
  21. 29 6月, 2004 1 次提交
  22. 28 11月, 2003 1 次提交
  23. 23 3月, 2003 1 次提交
  24. 21 3月, 2003 1 次提交
  25. 16 11月, 2002 1 次提交
  26. 14 11月, 2002 1 次提交
  27. 10 10月, 2002 1 次提交
  28. 09 10月, 2002 1 次提交
    • R
      Add a few more VxWorks targets. · 6a89a25c
      Richard Levitte 提交于
      Correct misspelled VXWORKS macros.
      Add VXWORKS identifying macros to e_os2.h.
      Add required inclusions and mappings for VxWorks in e_os.h.
      A few small modifications to make OpenSSL build and work on VxWorks.
      PR: 253, except for the  change that was handled in an earlier
               commit, and a request for easy build of just parts of OpenSSL.
      6a89a25c
  29. 14 6月, 2002 1 次提交
  30. 06 4月, 2002 1 次提交
  31. 27 9月, 2001 1 次提交
  32. 02 7月, 2001 1 次提交
  33. 14 5月, 2001 1 次提交
  34. 13 5月, 2001 2 次提交
  35. 12 5月, 2001 1 次提交
    • D
      · 595cc5b4
      Dr. Stephen Henson 提交于
      Under VC++ _DLL is set to indicate that the application
      will be linked against the DLL runtime library. It is
      automatically set when /MD is used.
      
      As a result OpenSSL shouldn't use _DLL to determine if
      it should set OPENSSL_OPT_WINDLL because this will
      cause linkage conflicts with static builds which do
      include the /MD compiler switch.
      595cc5b4
  36. 05 4月, 2001 1 次提交
  37. 05 3月, 2001 1 次提交
  38. 02 3月, 2001 1 次提交
    • 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