> > I'm not sure why you need to yank out source when it's just as easy to
> > link with libcrypto and make sure you only use the specific
> > algorithms. In such a case, one should avoid using things like
> > EVP_get_cipherbyname() since that requires that all compiled
> > algorithms be linked in.
>
> I was thinking more of environments where dynamic linking doesn't
> exist, or everything you need has to be stored in a limited amount of
> space like a floppy or some sort of solid-state memory device. This
> is somewhat common.
A good modular library will only link in the .o's that are necessary to build
a usable program. So it doesn't matter if you have libjpeg combined with
libssl, it won't increase the size of your program any (except maybe for
header info from the lib that could be stripped out of the binary).
So if you cross-compile on your PC and upload the binary to the smaller device
in question, there shouldn't be any problem.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
