AES x86_64 assembler implementation is available in HEAD now. The code
was benchmarked on Opteron CPU and exhibited 50% improvement over gcc
3.3.2. I wonder if somebody could compare them, compiler-generated and
hand-coded codes, on EM64T. To do so, grab latest openssl-SNAP-* at
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL PROTECTED]
asdasdasczxczxczx
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL PROTECTED]
123456
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL PROTECTED]
Hi,
I have attached 2 certificates (I have changed the extension to .txt as
the openssl forum does not accept .cer). The microsoft.txt is exported
from the browser and the david.txt is created by openssl and also
exported from the browser (IE).
The microsoft cert I can install on my
hi,
solaris compile with forte 7 C 5.4 here needs always 3-4 make until
it is done. make -j 10 does not work at all. is it expected to work
that way and its just a forte problem?
it was so for the older releases too, so nothing worse now :)
-solo
patch applied
Thanks,
Nils
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL
I am having a lot of problems importing a certificate made in openssl
into a phone, but I can get a keytool certificate imported. The only
thing is that I need to change the V1 cert (keytool only makes V1) to a
V3 cert - can openssl modify a cert to a V3 (without changing anything
else)?
cid:part1.07040304.05000705@ntlworld.comThanks, I have tried that now,
but still it does not work - I think the openssl generated cert either
adds some extra objects or it does not add some objects.
There may be a simpler option: I have created a cert using keytool that
does work on the phone,
