I'd love to see a list of the minimum algorithms to:
(or a maximum list of algorithms to exclude:-)

* Run https with a the majority of browsers
  (RSA, DES, 3DES, SHA-1 and RC-4 is my guess)
* Run openssh
* Get a libcrypto that supports both https and openssh

/Johan


----- Original Message -----
From: Greg Stark <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, March 15, 2001 16:37
Subject: Re: How to reduce size of OpenSSL LIB file


> Kim,
>
>     You can modify the do_masm.bat file in the ms\ directory. You need to
> tell the perl script util\mk1mf.pl which cryptogrpahy to eliminate. Here
is
> a fragment that could be in do_masm.bat showing one way to do it.
>
> SET SKIPS=no-rc5 no-bf no-cast no-idea no-ripemd no-dh no-dsa
> perl util\mk1mf.pl %SKIPS% VC-WIN32 >ms\nt.mak
>
> Look through the perl script and maybe a few other places to see what
no-***
> options are supported. Please post the results to the list. I think it is
of
> general interest.
>
> Good luck,
> _____________________________________
> Greg Stark
> Ethentica, Inc.
> [EMAIL PROTECTED]
> _____________________________________
>
>
>
> ----- Original Message -----
> From: "Hellan,Kim KHE" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, March 15, 2001 6:33 AM
> Subject: VS: How to reduce size of OpenSSL LIB file
>
>
> > Yes, in some applications (like COM objects) I'm statically linking,
> > because I need a "one-file" application.
> > In other apps. I use the DLL's.
> > I'm sure it is possible to exclude the code for some algorithms, I just
> > need to know how.
> >
> > Kim Hellan
> >
> >
> > You are statically linking libeay32.lib by the sounds of things.  It
> > would probably be better to make the dll and link in the stub library.
> > My libeay32.lib and libeay32.dll are 367KB and 645KB (debug)
> > respectively.
> >
> >
> > "Hellan,Kim KHE" wrote:
> > >
> > > I'm building a static OpenSSL library using MS VC++ 6 on Windows NT4.
> > > Using the standard OpenSSL makefiles this all works fine, but the
> > > libeay32.lib file becomes very big (about 2.3 MB for a release build
> > and 4
> > > MB for a debug build).
> > > This of course drastically increases the size of my applications when
> > this
> > > file is linked.
> > > Is there a way to exclude some code that I never use?
> > > Some algorithms like DSA or DH I never use (basically I only use 3DES
> > and
> > > RSA), so how can I exclude all this "unused" code when building the
> > lib?
> > >
> > > I can see that a lot of the code for example contains a NO_DSA define,
> > but
> > > how can I use this when building the lib.
> > >
> > > TIA
> > > Kim Hellan
> > > KMD / KMD-CA
> > > http://www.kmd-ca.dk
> > > Mailto:[EMAIL PROTECTED]
> > ______________________________________________________________________
> > OpenSSL Project                                 http://www.openssl.org
> > User Support Mailing List                    [EMAIL PROTECTED]
> > Automated List Manager                           [EMAIL PROTECTED]
>
> ______________________________________________________________________
> OpenSSL Project                                 http://www.openssl.org
> User Support Mailing List                    [EMAIL PROTECTED]
> Automated List Manager                           [EMAIL PROTECTED]
>

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to