> I would have thought that it should run faster with gmp.
Couple of comments about comparing openssl bn and gmp. It's recognized
fact that openssl bn has room for improvement. crypto/bn/asm/*-mont.pl
modules aim to fill this room. It should be noted however that openssl
bn is unlikely to outperfo
>> Well even though I get the error about the shared libraries, it did work
>> with is Configure:
>>
>> ./Configure --prefix=~gries/usr/local/ssl
>> --openssldir=~gries/usr/local/ssl threads linux-ppc64 -m64
>> -L/usr/local/lib -DOPENSSL_USE_GMP -lgmp -static
>>
>> [EMAIL PROTECTED]:~/ope
Robert Gries wrote:
> Well even though I get the error about the shared libraries, it did work with
> is Configure:
>
> ./Configure --prefix=~gries/usr/local/ssl --openssldir=~gries/usr/local/ssl
> threads linux-ppc64 -m64 -L/usr/local/lib -DOPENSSL_USE_GMP -lgmp -static
>
> [EMAIL PROTECT
No, this particular instruction is not a problem, as it's essentially
different ways to encode same thing (for reference, gnu assembler also
uses shorter encoding). But it's right track, because it appears that
metrowerks gets into trouble when the value exceeds 127. It fails to
recognize that in
Hi Andy,
> No, this particular instruction is not a problem, as it's essentially
> different ways to encode same thing (for reference, gnu assembler also
> uses shorter encoding). But it's right track, because it appears that
> metrowerks gets into trouble when the value exceeds 127. It fails to
>
Version: 0.9.8c
Summary: database file index.txt get malformed on large expiry date.
Description: We increased the expiration duration for new certificates
up to 365000 days (1000 years) since we noted that it is not nessecary
to have certificates which expires for our purpose.
When i signed the f
