Hi,
I'm considering porting OpenSSL to a RTOS, and would like to hear about
people's experience with such a task.
- How portable exactly is OpenSSL? Are all OS and platform specific
definitions and wrappers(?) placed in a single place or is this going to
require changing the code all-over?
Perhaps ccgost is using the BIGNUM library in a way that other routines
don't
and that is triggering a problem.
If so, should it be considered bug or feature of ccgost engine?
It's too early to answer that kind of question.
crypto/bn/asm/x86-mont.pl was heavily modified recently... As
On 2006.12.27 at 09:57:30 +0100, Andy Polyakov wrote:
turns to be culprit, then note that there are two code pathes, sse2 and
integer-only, the latter has separate squaring procedure, and we have to
figure out which one fails... To switch off squaring procedure, comment
out 'jz
should be fixed in the repository (0.9.8-stable and cvs head).
Please test a recent snapshot.
Thanks,
Nils
__
OpenSSL Project http://www.openssl.org
Development Mailing List
Hi Eitan,
- How portable exactly is OpenSSL? Are all OS and platform specific
definitions and wrappers(?) placed in a single place or is this going to
require changing the code all-over?
Basically OpenSSL is portable to any RTOS and the complexity depends on the
compiler and the options that
On 2006.12.27 at 09:57:30 +0100, Andy Polyakov wrote:
line #248 still reads as 'if(0)'. I'll have alook at the code, but there
might be need for test case, so could you provide sequence of commands
to reproduce the problem [or program if it was one].
Here small test programm is attached.
On Wed, Dec 27, 2006 at 10:44:08AM +0200, Bar, Eitan wrote:
Hi,
I'm considering porting OpenSSL to a RTOS, and would like to hear about
people's experience with such a task.
- How portable exactly is OpenSSL? Are all OS and platform specific
definitions and wrappers(?) placed in
same result is achieved without no-sse2 option - fail without commenting
line #273 and pass with it.
??? If you configure without no-sse2 and run on sse2 capable CPU, then
line #273 shouldn't affect result. What CPU and OS was the test executed on?
cat /proc/cpuinfo
flags : fpu vme
Now tests pass on my workstation. Next morning we'll see results on all
other platforms.
For reference. In order to test integer-only code paths on sse2 capable
system you can run test suite with OPENSSL_ia32cap environment variable
set to 0. In other words it's not necessary to have both
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
Hi there,
do you plan to implement signatures aggregation?
It would be an useful feature. Signature aggregation allows to combine
different signatures into a single one. The receiver, will be able to verify
the validity of each signature by analyzing just the aggregate.
There are different
(Sorry for the other email, I've found in the README file the
procedure to make contributions... as usual RTFM ;-) )
I've made an improvement on the CA application command line section
of OpenSSL and I'll be glad to share it with the community. The change
is very simple: I've added two new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
most HW engines are now moved to engines/ directory and compiled into
standalone libsomething.so modules. Except for the PadLock engine.
That's still in crypto/engine/ and linked directly into libcrypto.so.
However the initialization code in
13 matches
Mail list logo
