On Sat, 20 Apr 2002, Richard Levitte - VMS Whacker wrote:
> dkaufman> The problem is that util/mklink.pl only works with algorithms that
> dkaufman> are included in the build. It is called from the makefile in each
>
> In that case, it's the test programs that need to be changed so as not
> to get built with any tests if the algorithm tested isn't present.
>
> In any case, shouldn't linking with libcrypto.a produce linker errors
> if you try to get algorithms that aren't there?
The test files are designed to report if the algorithm is not
supported, and do not attempt to use the excluded algorithm. This
provides additional security, since otherwise the algorithm might have
been accidentally excluded when it was intended to be part of openssl.
Since all the test files were constructed this way, it seemed there
was an intent to compile and test with test files whose algorithm was
excluded from the compilation. Hence I made an effort to make sure
that these files were available, even when the algorithm was excluded,
rather than avoiding the test. A sample from rc5test.c
follows:
#ifdef NO_RC5
int main(int argc, char *argv[])
{
printf("No RC5 support\n");
return(0);
}
I'll resubmit the patches with the shell scripts fixed in separate
posts.
Doug
__
Doug Kaufman
Internet: [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
