1. 08 3月, 2001 1 次提交
  2. 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
  3. 23 2月, 2001 1 次提交
  4. 22 2月, 2001 1 次提交
  5. 21 2月, 2001 2 次提交
  6. 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
  7. 05 2月, 2001 1 次提交
  8. 28 12月, 2000 1 次提交
  9. 15 12月, 2000 1 次提交
    • G
      This is an engine contributed by Broadcom - it is meant to support the · 016d7d25
      Geoff Thorpe 提交于
      BCM5805 and BCM5820 units. So far I've merely taken a skim over the code
      and changed a few things from their original contributed source
      (de-shadowing variables, removing variables from the header, and
      re-constifying some functions to remove warnings). If this gives
      compilation problems on any system, please let me know. We will hopefully
      know for sure whether this actually functions on a system with the relevant
      hardware in a day or two.  :-)
      016d7d25
  10. 05 12月, 2000 1 次提交
  11. 16 11月, 2000 2 次提交
    • G
      I have no idea how this comment got there, but it's certainly not · 8bfc8f93
      Geoff Thorpe 提交于
      applicable to ENGINE_ctrl()
      8bfc8f93
    • G
      Many applications that use OpenSSL with ENGINE support might face a · ef02b10a
      Geoff Thorpe 提交于
      situation where they've initialised the ENGINE, loaded keys (which are then
      linked to that ENGINE), and performed other checks (such as verifying
      certificate chains etc). At that point, if the application goes
      multi-threaded or multi-process it creates problems for any ENGINE
      implementations that are either not thread/process safe or that perform
      optimally when they do not have to perform locking and other contention
      management tasks at "run-time".
      
      This defines a new ENGINE_ctrl() command that can be supported by engines
      at their discretion. If ENGINE_ctrl(..., ENGINE_CTRL_HUP,...) returns an
      error then the caller should check if the *_R_COMMAND_NOT_IMPLEMENTED error
      reason was set - it may just be that the engine doesn't support or need the
      HUP command, or it could be that the attempted reinitialisation failed. A
      crude alternative is to ignore the return value from ENGINE_ctrl() (and
      clear any errors with ERR_clear_error()) and perform a test operation
      immediately after the "HUP". Very crude indeed.
      
      ENGINEs can support this command to close and reopen connections, files,
      handles, or whatever as an alternative to run-time locking when such things
      would otherwise be needed. In such a case, it's advisable for the engine
      implementations to support locking by default but disable it after the
      arrival of a HUP command, or any other indication by the application that
      locking is not required. NB: This command exists to allow an ENGINE to
      reinitialise without the ENGINE's functional reference count having to sink
      down to zero and back up - which is what is normally required for the
      finish() and init() handlers to get invoked. It would also be a bad idea
      for engine_lib to catch this command itself and interpret it by calling the
      engine's init() and finish() handlers directly, because reinitialisation
      may need special handling on a case-by-case basis that is distinct from a
      finish/init pair - eg. calling a finish() handler may invalidate the state
      stored inside individual keys that have already loaded for this engine.
      ef02b10a
  12. 14 11月, 2000 1 次提交
  13. 13 11月, 2000 1 次提交
  14. 09 11月, 2000 1 次提交
  15. 07 11月, 2000 5 次提交
  16. 04 11月, 2000 2 次提交
  17. 03 11月, 2000 1 次提交
    • R
      Change the engine library so the application writer has to explicitely · 11c0f120
      Richard Levitte 提交于
      load the "external" built-in engines (those that require DSO).  This
      makes linking with libdl or other dso libraries non-mandatory.
      
      Change 'openssl engine' accordingly.
      
      Change the engine header files so some declarations (that differed at
      that!) aren't duplicated, and make sure engine_int.h includes
      engine.h.  That way, there should be no way of missing the needed
      info.
      11c0f120
  18. 27 10月, 2000 1 次提交