You need to sign in or sign up before continuing.
  1. 11 5月, 2007 1 次提交
  2. 20 12月, 2006 1 次提交
  3. 03 9月, 2005 3 次提交
  4. 02 9月, 2005 2 次提交
  5. 01 9月, 2005 1 次提交
  6. 23 4月, 2005 1 次提交
  7. 16 3月, 2004 1 次提交
  8. 30 10月, 2003 1 次提交
  9. 21 3月, 2003 1 次提交
  10. 21 10月, 2002 1 次提交
  11. 03 10月, 2002 1 次提交
  12. 27 7月, 2001 1 次提交
    • D
      · 1241126a
      Dr. Stephen Henson 提交于
      More linker bloat reorganisation:
      
      Split private key PEM and normal PEM handling. Private key
      handling needs to link in stuff like PKCS#8.
      
      Relocate the ASN1 *_dup() functions, to the relevant ASN1
      modules using new macro IMPLEMENT_ASN1_DUP_FUNCTION. Previously
      these were all in crypto/x509/x_all.c along with every ASN1
      BIO/fp function which linked in *every* ASN1 function if
      a single dup was used.
      
      Move the authority key id ASN1 structure to a separate file.
      This is used in the X509 routines and its previous location
      linked in all the v3 extension code.
      
      Also move ASN1_tag2bit to avoid linking in a_bytes.c which
      is now largely obsolete.
      
      So far under Linux stripped binary with single PEM_read_X509
      is now 238K compared to 380K before these changes.
      1241126a
  13. 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
  14. 23 2月, 2001 2 次提交
  15. 16 2月, 2001 1 次提交
  16. 31 12月, 2000 1 次提交
  17. 14 12月, 2000 1 次提交
  18. 09 12月, 2000 1 次提交
    • D
      · 9d6b1ce6
      Dr. Stephen Henson 提交于
      Merge from the ASN1 branch of new ASN1 code
      to main trunk.
      
      Lets see if the makes it to openssl-cvs :-)
      9d6b1ce6