Skip to content
  1. Nov 28, 2003
    • Richard Levitte's avatar
      Make a number of changes to the OS/2 build. Submitter's comment below. · 9d68b289
      Richard Levitte authored
      PR: 732
      Submitted by: Ilya Zakharevich <nospam-abuse@ilyaz.org>
      
      Submitter's comment:
      
      This patch:
      
      a) Introduces a new file os2/backwardify.pl.
      
      b) Introduces a new mk1mf.pl variable $preamble.  As you can see, it may
         be used also to move some OS-specific code to VC-CE too (the the
         first chunk of the patch);
      
      c) The DESCRIPTION specifier of the .def file is made more informative:
         now it contains the version number too.  On OS/2 it is made conformant
         to OS/2 conventions; in particular, when one runs the standard command
      	BLDLEVEL this.DLL
         one can see:
      
         Vendor:      www.openssl.org/
         Revision:    0.9.7c
         Description: OpenSSL: implementation of Secure Socket Layer; DLL for library crypto.  Build for EMX -Zmtd
      
         [I did not make Win32 descriptions as informative as this - I'm afraid to
          break something.  Be welcome to fix this.]
      
      d) On OS/2 the generated DLL was hardly usable (it had a shared initialized
         data...
      9d68b289
    • Richard Levitte's avatar
      Let's use text/plain in the example instead of crapy HTML. · eb5f555f
      Richard Levitte authored
      PR: 777
      Submitted by: Michael Shields <mshields@sunblocksystems.com>
      eb5f555f
  2. Nov 27, 2003
    • Richard Levitte's avatar
      If dynamically-loadable ENGINEs are linked against a shared-library version · 04dc4edb
      Richard Levitte authored
      of libcrypto, then it is possible that when they are loaded they will share
      the same static data as the loading application/library. This means it will
      be too late to set memory/ERR/ex_data/[etc] callbacks, but entirely
      unnecessary to try.
      
      This change (and a great part of this comment) was implemented in
      0.9.8-dev a long time ago, but slightly differently.  In 0.9.8-dev, a
      specific function that just returns a pointer to some static object is
      used. For 0.9.7x, we couldn't do that, since the way we handle feature
      freezes is, among other, to not add any more non-static functions.
      Instead, we use the function ERR_get_implementation() and compare the
      returned value with fns->err_fns, a member of fns that already is
      there, and which therefore can safely be used in this manner.
      
      What happens is that if the loaded ENGINE's return value from this
      function matches the loading application/library's return value - they
      share static data. If they don't match, the loaded ENGINE has its own
      copy of libcrypto's static data and so the callbacks need to be set.
      04dc4edb
  3. Nov 24, 2003
  4. Nov 22, 2003
  5. Nov 20, 2003
  6. Nov 19, 2003
  7. Nov 18, 2003
  8. Nov 16, 2003
  9. Nov 10, 2003
  10. Oct 29, 2003
  11. Oct 15, 2003
  12. Oct 11, 2003
  13. Oct 10, 2003
  14. Oct 07, 2003
  15. Oct 02, 2003
  16. Oct 01, 2003
  17. Sep 30, 2003
  18. Sep 29, 2003
  19. Sep 28, 2003
  20. Sep 27, 2003