I'm looking into http://gcc.gnu.org/PR19923
which claims that gcc-4.0 is slower on 'openssl speed'
than earlier versions. The only huge regression seems
to be in md2. ...
I'm interested in the observed performance regression even with the
hand-coded assembly; that simply should not be happeni
Andy Polyakov wrote:
I'm looking into http://gcc.gnu.org/PR19923
which claims that gcc-4.0 is slower on 'openssl speed'
than earlier versions. The only huge regression seems
to be in md2. ...
I'm interested in the observed performance regression even with the
hand-coded assembly; that simply
Quoting of DEVRANDOM after DOS DJGPP changes in crypto/rand/rand_unix.c
my break all other platforms, except OpenBSD.
Result is file with name "DEVRANDOM" instead of list defined in e_os.h.
The test case:
=
#include
#include
#include
i
Robinson, Herbie via RT wrote:
If one wants to assert that the caller didn't provide arguments that overflowed, wouldn't the assertion be
assert (h < d);
If one is just going to assert that the initial normalizing shift doesn't overflow, then shouldn't the assertion be
asser
On Tue, 31 May 2005, Charles Bailey wrote:
> The helper script utils/point.sh creates self-referential links on a
> case-insensitive filesystem (such as HFS+) when given two file names which
> differ only in alphabetic case. The attached patch resolves the issue by
> causing it to skip any pai
On Tue, 31 May 2005, Doug Kaufman wrote:
> On Tue, 31 May 2005, Andy Polyakov wrote:
>
> > The latter proposed change, quoting DEVRANDOM, shall have adverse effect
> > on other platforms. Can you elaborate on the error during compilation
> > instead? As for mtu and sock_type. Is it possible to
> Environment: openssl-0.9.8-beta3, ULTRIX 4.5, default shell
>
> ULTRIX's default shell (/bin/sh) is "a bit special", so I don't expect
> to get this fixed. But for reference (and because these problems only
> exist since openssl-0.9.7f) I'll report them:
>
> (1) "test -x" unsupported (util/ope
The helper script utils/point.sh creates self-referential links on a
case-insensitive filesystem (such as HFS+) when given two file names which
differ only in alphabetic case. The attached patch resolves the issue by
causing it to skip any pair of names which already point to the same file.
-
I spent several hours (my estimate is between 10 and 16) running "openssl
dhparam -out ~/
Desktop/dhparam.txt 4224". After finally completing, it told me that
~/Desktop/dhparam.txt
doesn't exist, and my progress was thrown out.
First, ~/Desktop/ certainly exists and has write access, so I'm no
If one wants to assert that the caller didn't provide arguments that
overflowed, wouldn't the assertion be
assert (h < d);
If one is just going to assert that the initial normalizing shift doesn't
overflow, then shouldn't the assertion be
assert((i == BN_BITS2) || (h < (BN_U
Hello!
On Wed, 1 Jun 2005, Jostein Tveit wrote:
"Dmitry Belyavsky via RT" <[EMAIL PROTECTED]> writes:
I use 0.9.8-stable-SNAP-20050601 snapshot. Problem occurs on digest
signing.
This seems to be the same bug as I reported just a couple of
hours ago on openssl-dev.
(Se p
I use 0.9.8-stable-SNAP-20050601 snapshot. Problem occurs on digest
signing.
This seems to be the same bug as I reported just a couple of
hours ago on openssl-dev.
Try to see if you get the same error as me if you apply the error
checking patch:
OpenSSL request tracker and <[EMAIL PROTEC
"Dmitry Belyavsky via RT" <[EMAIL PROTECTED]> writes:
> I use 0.9.8-stable-SNAP-20050601 snapshot. Problem occurs on digest
> signing.
This seems to be the same bug as I reported just a couple of
hours ago on openssl-dev.
(Se post with subject "openssl-0.9.8-beta3,
Environment: openssl-0.9.8-beta3, ULTRIX 4.5, default shell
ULTRIX's default shell (/bin/sh) is "a bit special", so I don't expect
to get this fixed. But for reference (and because these problems only
exist since openssl-0.9.7f) I'll report them:
(1) "test -x" unsupported (util/opensslwrap.sh)
Environment: openssl-0.9.8-beta3, ULTRIX 4.5, ultrix-gcc (gcc 2.95.3)
On this platform, gcc 2.95.3 supports 64-bit integer. To enable SHA512
(and avoid the "undefined BN_ULLONG" problem in pqueue.c) only the
following change was necessary:
- Configure (line 497, insert BN_LLONG)
"ultrix-gcc"
Hello!
I use 0.9.8-stable-SNAP-20050601 snapshot. Problem occurs on digest
signing.
make report:
OpenSSL self-test report:
OpenSSL version: 0.9.8-beta4-dev
Last change: Correct naming of the 'chil' and '4758cca' ENGINEs. Thi...
Options: -g enable-s
ok, ticket resolved.
Cheers,
Nils
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [
Thank you so much for your help.
"X509_free(peer);" was the solution.
Please consider this case closed.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Nils Larsch via
RT
Sent: Tuesday, May 31, 2005 4:17 PM
To: Karim Sharif
Cc: openssl-dev@openssl.o
Hi, OpenSSL developers.
I try to compile openssl-0.9.8-beta3 on Solaris 8, using 64-bit
Sun Forte compiler (cc: Sun C 5.7 2005/01/07)
When doing 'make test' I get a core dump. But after applying a
simple patch, I am unable to track down the bug any further.
The Solaris PRNG patch 112438 (as ment
ok, I've committed a fix with which SSL_load_client_CA_file
should clear the error queue on success. Please test a recent
snapshot.
Thanks,
Nils
__
OpenSSL Project http://www.openssl.org
Developmen
Hi,
Here is a testlog for OpenBSD -current. We probably won't get around to
integrating 0.9.8 until after OpenBSD-3.8 is released.
I hacked the 'test skipped' stuff our of util/selftest.pl - I think skipping
tests because of no-mdc2 and no-rc5 is somewhat self-defeating
-d
OpenSSL self-test r
21 matches
Mail list logo
