Skip to content
Snippets Groups Projects
  1. Dec 20, 2002
  2. Nov 27, 2002
  3. Oct 09, 2002
  4. Aug 09, 2002
    • Bodo Möller's avatar
      Add ECDH support. · e172d60d
      Bodo Möller authored
      Additional changes:
       - use EC_GROUP_get_degree() in apps/req.c
       - add ECDSA and ECDH to apps/speed.c
       - adds support for EC curves over binary fields to ECDSA
       - new function EC_KEY_up_ref() in crypto/ec/ec_key.c
       - reorganize crypto/ecdsa/ecdsatest.c
       - add engine support for ECDH
       - fix a few bugs in ECDSA engine support
      
      Submitted by: Douglas Stebila <douglas.stebila@sun.com>
      e172d60d
  5. Jul 31, 2002
  6. Jul 30, 2002
  7. Jun 27, 2002
  8. Jun 10, 2002
  9. May 30, 2002
  10. May 02, 2002
  11. Feb 13, 2002
  12. Jan 02, 2002
    • Richard Levitte's avatar
      Because Rijndael is more known as AES, use crypto/aes instead of · 6f9079fd
      Richard Levitte authored
      crypto/rijndael.  Additionally, I applied the AES integration patch
      from Stephen Sprunk <stephen@sprunk.org> and fiddled it to work
      properly with the normal EVP constructs (and incidently work the same
      way as all other symmetric cipher implementations).
      
      This results in an API that looks a lot like the rest of the OpenSSL
      cipher suite.
      6f9079fd
  13. Oct 30, 2001
  14. Oct 04, 2001
  15. Aug 05, 2001
  16. Jun 05, 2001
  17. May 16, 2001
  18. May 06, 2001
  19. Mar 09, 2001
  20. Mar 08, 2001
  21. Mar 05, 2001
  22. Feb 22, 2001
  23. Feb 21, 2001
  24. Feb 19, 2001
    • Richard Levitte's avatar
      Make all configuration macros available for application by making · cf1b7d96
      Richard Levitte authored
      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
    • Richard Levitte's avatar
      make update · 07247321
      Richard Levitte authored
      07247321
    • Bodo Möller's avatar
      Add uid.{c,o} · 0f863149
      Bodo Möller authored
      0f863149
  25. Dec 29, 2000
  26. Oct 26, 2000
  27. Oct 14, 2000
  28. Sep 25, 2000
  29. Sep 07, 2000
  30. Jun 13, 2000
  31. Apr 04, 2000
    • Geoff Thorpe's avatar
      This commit ties the new DSO code (crypto/dso/) into the build for a · 9ec0126e
      Geoff Thorpe authored
      variety of platforms. A few are missing, and they will be added in
      eventually, but as this is new stuff, it was better to not break lots of
      platforms in one go that we can't easily test. The changes to "Configure"
      should illustrate how to add support to other systems if you feel like
      having a go.
      
      NB: I'll add something shortly to allow you to add "dlfcn.h" support on
      those platforms that don't have (or need) a dlfcn.h header file. (The
      symbol for Configure will probably by "dlfcn_no_h").
      
      Thanks to Richard Levitte, who is responsible for the dso_dl.c support,
      understanding the trickier aspects of the build process, and giving great
      feedback on everything else.
      
      [Don't use this stuff if you're easily offended by changes to the
      interface or behaviour - it's still work in progress.]
      
      PR:
      9ec0126e
  32. Mar 20, 2000
  33. Feb 01, 2000
  34. Jan 23, 2000
    • Dr. Stephen Henson's avatar
      · dd9d233e
      Dr. Stephen Henson authored
      Tidy up CRYPTO_EX_DATA structures.
      dd9d233e
  35. Jan 07, 2000
  36. Dec 17, 1999
    • Richard Levitte's avatar
      Rebuild of the OpenSSL memory allocation and deallocation routines. · 9ac42ed8
      Richard Levitte authored
      With this change, the following is provided and present at all times
      (meaning CRYPTO_MDEBUG is no longer required to get this functionality):
      
        - hooks to provide your own allocation and deallocation routines.
          They have to have the same interface as malloc(), realloc() and
          free().  They are registered by calling CRYPTO_set_mem_functions()
          with the function pointers.
      
        - hooks to provide your own memory debugging routines.  The have to
          have the same interface as as the CRYPTO_dbg_*() routines.  They
          are registered by calling CRYPTO_set_mem_debug_functions() with
          the function pointers.
      
      I moved everything that was already built into OpenSSL and did memory
      debugging to a separate file (mem_dbg.c), to make it clear what is
      what.
      
      With this, the relevance of the CRYPTO_MDEBUG has changed.  The only
      thing in crypto/crypto.h that it affects is the definition of the
      MemCheck_start and MemCheck_stop macros.
      9ac42ed8
  37. Sep 10, 1999
Loading