There is a problem building OpenSSL on a 8+3 filesystem like
DOS due to the files:
engines/ccgost/gost2001.c
engines/ccgost/gost2001_keyx.c
The latter overwrites the first using djgpp's tar. Could you please
rename them to something like:
engines/ccgost/gost01.c
engines/ccgost/gost01_keyx.c
so
On 2007.01.04 at 16:57:35 +0100, Gisle Vanem wrote:
There is a problem building OpenSSL on a 8+3 filesystem like
DOS due to the files:
engines/ccgost/gost2001.c
engines/ccgost/gost2001_keyx.c
Sorry, when I named files I haven't thought than anybody still use real
DOS with no long names
Guys,
I've written some ARM assembler and would like to benchmark it. So if
anybody on the list has access to linux-arm hardware, please contact me
for instructions. A lot of thanks in advance. A.
__
OpenSSL Project
Engine is moved to ./engine in HEAD, but in 098 I've chosen more
conservative eng_all.c-only patch. A.
__
OpenSSL Project http://www.openssl.org
Development Mailing List
there is a cpuid test in rc4_skey.c which tests the hyperthreading cpuid
bit to distinguish between two implementations of rc4... unfortunately
this fails to properly distinguish the cpus. all dual core cpus (intel or
amd) report HT support even if they don't use symmetric-multithreading
like
Hi,
I am experimenting with a CAVIUM SSL hardware accelerator, and there seems
to be two ways to use the hardware.
One option is through OpenSSL Engine interface. The other option is by using
their proprietary TurboSSL library, which appears to be a port of OpenSSL.
I do see more work involved
On Fri, 5 Jan 2007, Andy Polyakov wrote:
there is a cpuid test in rc4_skey.c which tests the hyperthreading cpuid bit
to distinguish between two implementations of rc4... unfortunately this
fails to properly distinguish the cpus. all dual core cpus (intel or amd)
report HT support even
