1. 14 1月, 2016 1 次提交
    • V
      Fix DES_LONG breakage · bdb1d0c2
      Viktor Dukhovni 提交于
      For some strange reason opensslconf.h was only defining DES_LONG
      when included via des.h, but that's exceedingly fragile (as a
      result of include guards the include via des.h might not actually
      process the content again).
      
      Ripped out the nesting constraint, now always define OSSL_DES_LONG
      if not already defined.  Note, this could just be DES_LONG, but
      trying to avoid exposing DES_LONG in places where it has never been
      seen before, so it is up to des.h to actually define DES_LONG as
      OSSL_DES_LONG.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      bdb1d0c2
  2. 01 4月, 2015 1 次提交
  3. 03 2月, 2015 1 次提交
  4. 28 1月, 2015 1 次提交
  5. 27 1月, 2015 1 次提交
  6. 22 1月, 2015 1 次提交
  7. 20 5月, 2008 1 次提交
  8. 29 1月, 2004 1 次提交
  9. 21 3月, 2003 1 次提交
  10. 11 12月, 2002 1 次提交
    • R
      Since HEADER_DES_H has been the protector of des.h since libdes · 005ef84c
      Richard Levitte 提交于
      (before SSLeay, maybe?), it's better to have that macro protect
      the compatibility header des_old.h.  In the new des.h, let's use
      a slightly different protecting macro.
      
      The rationale is that there are application that might include (via
      other header files, perhaps) both an old libdes des.h and OpenSSL's
      des.h.  Whichever comes first would overshadow the other because of
      the clash in protecting macro.  This fix solves that problem.
      005ef84c
  11. 26 3月, 2002 2 次提交
  12. 06 2月, 2002 1 次提交
    • R
      With the changed des_old API, let's complete the work by renaming the · 44bdb056
      Richard Levitte 提交于
      functions in ui_compat.  This gave reason to rework that part more
      thoroughly, so here are the changes made:
      
      1. Add DES_read_password() and DES_read_2passwords() with the same
         functionality as the corresponding old des_ functions, as a
         convenience to the users.
      2. Add UI_UTIL_read_pw_string() and UI_UTIL_read_pw() with the
         functionality from des_read_pw_string() and des_read_pw(), again as
         a concenience to the users.
      3. Rename des_read_password(), des_read_2passwords(),
         des_read_pw_string() and des_read_pw() by changing des_ to
         _ossl_old_des_, and add the usual mapping macros.
      4. Move the implementation of des_read_password() and
         des_read_2passwords() to the des directory, since they are tightly
         tied to DES anyway.
      
      This change was inspired by a patch from Assar Westerlund <assar@sics.se>:
      
      There are some functions that didn't get the kick-away-old-des-and-
      replace-des-with-DES action.  Here's a patch that adds DES_ and des_
      (in des_old.h) versions of des_read_pw_string et al.  This patch
      includes some of the first des_old.h semi-colon macro fixes that I've
      already sent.
      44bdb056
  13. 25 1月, 2002 1 次提交
    • B
      New functions · a14e2d9d
      Bodo Möller 提交于
          ERR_peek_last_error
          ERR_peek_last_error_line
          ERR_peek_last_error_line_data
      (supersedes ERR_peek_top_error).
      
      Rename OPENSSL_NO_OLD_DES_SUPPORT into OPENSSL_DISABLE_OLD_DES_SUPPORT
      because OPENSSL_NO_... indicates disabled algorithms (according to
      mkdef.pl).
      a14e2d9d
  14. 23 1月, 2002 1 次提交
  15. 25 10月, 2001 2 次提交
  16. 07 9月, 2001 1 次提交
  17. 31 7月, 2001 2 次提交
  18. 13 5月, 2001 2 次提交
  19. 29 3月, 2001 1 次提交
    • R
      Since there has been reports of clashes between OpenSSL's · 080b8cad
      Richard Levitte 提交于
      des_encrypt() and des_encrypt() defined on some systems (Solaris and
      Unixware and maybe others), we rename des_encrypt() to des_encrypt1().
      This should have very little impact on external software unless
      someone has written a mode of DES, since that's all des_encrypt() is
      meant for.
      080b8cad
  20. 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
  21. 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
  22. 31 12月, 2000 1 次提交
  23. 21 12月, 2000 1 次提交
    • D
      Various Win32 related fixes. Doesn't compile yet on · 3c07b4c2
      Dr. Stephen Henson 提交于
      Win32 but it is getting there...
      
      Update mkdef.pl to handle ASN1_ANY and fix headers.
      
      Stop various VC++ warnings.
      
      Include some fixes from "Peter 'Luna' Runestig"
      <peter@runestig.com>
      
      Remove external declaration for des_set_weak_key_flag:
      it doesn't exist.
      3c07b4c2
  24. 01 6月, 2000 1 次提交
  25. 02 5月, 2000 1 次提交
  26. 19 3月, 2000 1 次提交
  27. 06 2月, 2000 1 次提交
  28. 04 12月, 1999 1 次提交
    • B
      Add functions des_set_key_checked, des_set_key_unchecked. · cddfe788
      Bodo Möller 提交于
      Never use des_set_key (it depends on the global variable des_check_key),
      but usually des_set_key_unchecked.
      Only destest.c bothered to look at the return values of des_set_key,
      but it did not set des_check_key -- if it had done so,
      most checks would have failed because of wrong parity and
      because of weak keys.
      cddfe788
  29. 30 7月, 1999 1 次提交
  30. 29 7月, 1999 2 次提交
  31. 10 6月, 1999 1 次提交
  32. 09 6月, 1999 1 次提交
  33. 08 6月, 1999 1 次提交
  34. 17 5月, 1999 1 次提交
  35. 16 5月, 1999 1 次提交
    • B
      Change type of various DES function arguments from des_cblock · edf0bfb5
      Bodo Möller 提交于
      (meaning pointer to char) to des_cblock * (meaning pointer to
      array with 8 char elements), which allows the compiler to
      do more typechecking.  (The changed argument types were of type
      des_cblock * back in SSLeay, and a lot of ugly casts were
      used then to turn them into pointers to elements; but it can be
      done without those casts.)
      
      Introduce new type const_des_cblock -- before, the pointers rather
      than the elements pointed to were declared const, and for
      some reason gcc did not complain about this (but some other
      compilers did).
      edf0bfb5