----- Original Message -----
From: "Neville Franks" <[EMAIL PROTECTED]>
To: "John Stewart" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, May 15, 2003 7:04 PM
Subject: Re[2]: trying to make my crypto++ using executable smaller


> I'm using Crypto++ V4.1 linked statically to my .EXE (see sig) and I
> don't recall there being the sort of jump in size you seeing.

    I could imagine 4.1 being a bit smaller.  Do you know off hand if it can
do the SHA1/RSA signature verification with PKCS style padding the same as
is in 5.1?

> You can't readily equate the size of the .lib to the size of the
> executable code as it contains a large amount of data which won't be
> included and also .obj info is bigger than the compiled code it
> produces. And there is a lot of other stuff in the .lib.

    All true :)

> If you are doing a debug build the .dll/.exe will have lots of extra
> debug info in it, which won't be present in a release build. Maybe
> that's what you are seeing.

    Nope, it's not a debug build.

> I'd suggest having a look at the VC6 .map file for the DLL which will
> show you exactly what is being dragged in from the .lib.

    I've glanced at it a bit but I just started looking at a bit more
intently when I noticed the test exe I made was dragging in some of the C++
file I/O library.  I was looking at the assembly to see if I could figure
out the 13000 byte growth discrepency between the .exe and .dll and I saw it
initializing itself.  It also looks like it's dragging in some smallish
portion of the C++ string library.  But together it looks like they're less
than 20k of the size increase at least in the code segment.  So the
220000ish byte size increase is not entirely due to the inclusion of the
crypto++ signature code, but the majority still seems to be.

    I definately appreciate the help with general size optimization info and
such.  But the primary question I want help with is how I should go about
replacing RSASSA_PKCS1v15_SHA_Verifier and VerifierFilter with something
that only decrypts the signature and removes the PKCS padding.  That way I
can directly see how much space if any I can save with such an approach.  Is
there some stripped down class that does what I want or do I need to build
it myself from the primitives?

    Thanks yet again,

    John Stewart





Reply via email to