Skip to content
  1. Dec 10, 2003
  3. Dec 03, 2003
  5. Dec 01, 2003
  7. Nov 29, 2003
  9. Nov 28, 2003
    • Richard Levitte's avatar
      RSA_size() and DH_size() return the amount of bytes in a key, and we · 6a6a08cb
      Richard Levitte authored 
      compared it to the amount of bits required...
PR: 770
Submitted by: c zhang <czhang2005@hotmail.com>
      6a6a08cb
    • Richard Levitte's avatar
      1024 is the export key bits limit according to current regulations, not 512. · 753cbc28
      Richard Levitte authored 
      PR: 771
Submitted by: c zhang <czhang2005@hotmail.com>
      753cbc28
    • 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 segment).

e) On OS/2 the generated DLLs had names like ssl.dll.  However, DLL names on
   OS/2 are "global data".  It is hard to have several DLLs with the same
   name on the system.  Thus this precluded coexistence of OpenSSL with DLLs
   for other SLL implementations - or other name clashes.  I transparently
   changed the names of the DLLs to open_ssl.dll and cryptssl.dll.

f) The file added in (a) is used to create "forwarder" DLLs, so the
   applications expecting the "old" DLL names may use the new DLLs
   transparently.  (A presence of these DLLs on the system nullifies (e),
   but makes old applications work.  This is a stopgap measure until the
   old applications are relinked.  Systems with no old applications do not
   need these DLLs, so may enjoy all the benefits of (e).)

   The new DLLs are placed in os2/ and os2/noname subdirectories.

g) The makefiles created with os2/OS2-EMX.cmd did not work (some mysterious
   meaningless failures).  The change to util/pl/OS2-EMX.pl uses the
   variable introduced in (b) to switch the Makefiles to SHELL=sh syntax.
   All these backslashes are removed, and the generated Makefiles started to
   work.

h) Running os2/OS2-EMX.cmd now prints out what to do next.
      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
  11. 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
  13. Nov 24, 2003
  15. Nov 22, 2003
  17. Nov 20, 2003
  19. Nov 19, 2003
  21. Nov 18, 2003
  23. Nov 16, 2003
  25. Nov 10, 2003
  27. Oct 29, 2003
  29. Oct 15, 2003
  31. Oct 11, 2003
  33. Oct 10, 2003
  35. Oct 07, 2003
  37. Oct 02, 2003
  39. Oct 01, 2003
  41. Sep 30, 2003
  43. Sep 29, 2003