> I've tried installing OpenSSL 0.9.8h from source on several FreeBSD
> 4.x systems, but they all fail the same test while running 'make test'
> after a successful compile (this is on FreeBSD 4.4 on an i386):
>
> $ ./config -d --prefix=/usr --openssldir=/etc/ssl shared
> $ gmake
> [...]
> $ gm
Problem is resolved by http://cvs.openssl.org/chngview?
cn=17335. I apologize for inconvenience. A.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-
>in "Configure", line 415, we see AR option "-X 64". There should
> not be space, so correct one is "-X64".
It was there for years [and was working for me at numerous occasions].
How come it doesn't for you? What's your AIX version? As for
"illegality." AIX manual page appears to be permitting
> You should not touch the file sha1-586.pl
sha1-586.pl was back-ported from in-development HEAD branch and extra
argument is a left-over and *should not* be there.
> because the problem is located
> in the file x86ms.pl that is dedicated to MASM. In this file, the line 273
> containing "$extra"
> I found the solution to this bug. The Mac Intel should be little endian, not
> big endian.
As was mentioned on openssl-dev, it's known problem, but unfortunately
modifying FIPS 1.1.2 code is not an option. The problem was addressed
earlier in regular branches. Case is being dismissed. A.
_
Andy,
I resolved the problem by changing the endian flag for Intel Macs in the
configure file. See my note below. Perhaps, this change to the configure
file can be included in future releases.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
For the Intel Mac, change the
> We're implementing our own web-server intended to run on Win32 platform
> and using OpenSSL for TLS/SSL support. We're obliged to be
> FIPS-certified and we're using OpenSSL 0.9.7 with FIPS module for these
> purposes. Recently, we were requested to support amd64 platform. I've
> tried to build O
> It's awfully hard to investigate a problem or find workarounds for a problem
> when the only description you have is "it failed to build successfully".
> Perhaps I could find a way to avoid the modifications you needed, except you
> don't tell me what they are.
Don't expect RT submitters to b
> I tried to build first build openssl-0.9.8e for win 64 using perl
> Configure VC-WIN64A and it failed saying that pthread.h is not found so
> I decided to try 0.9.8f which is building fine.
>
> Now I decided to build the shared library version but when I typed “perl
> Configure VC-WIN64A shared”
Andy,
I resolved the problem by changing the endian flag for Intel Macs in the
configure file. See my note below. Perhaps this change to the configure file
can be included in future releases.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
For the Intel Mac, change the
> Here's a patch against today's snapshot of head.
>
>>> I think that you has to compile with -DWIN32_LEAN_AND_MEAN in
>>> Configure before to do some undefs in openssl headers.
>
> I'm not really convinced, but for the time being, I've added that
> compile
> option to get rid of that more or les
Hi Stephen,
"Dr. Stephen Henson" <[EMAIL PROTECTED]> writes:
> Well RSA_private_encrypt() despite its name is a signing
> operation. There is a PKCS#11 equivalent (C_Sign and the CKM_RSA_PKCS
> mechanism) though some tokens don't support it fully but emulate it in
> such a way that it only works
Hi,
Sorry to bother, but just a quick question: those new threadid
handling routines that got into 0.9.9 a while ago disappeared from the
latest CVS (today) again. I assume this is intentional?
Just a Yes/No 's all I crave.
Thanks for answering and keep it up!
--
Met vriendelijke groeten / Best
On Wednesday 16 July 2008 16:58:11 Ger Hobbelt wrote:
> Hi,
>
> Sorry to bother, but just a quick question: those new threadid
> handling routines that got into 0.9.9 a while ago disappeared from the
> latest CVS (today) again. I assume this is intentional?
> Just a Yes/No 's all I crave.
>
> Thank
Hi,
I have sent this mail once before, tell me if it's offtopic or where
should I ask about contributing to OpenSSL.
I have developed library based on OpenSSL 0.9.8 that implemented ETSI
standard for long term signatures. It allows electronic signatures to
be valid for long period of time (many ye
On July 17, 2008 03:19:54 pm Tomas Vrabel wrote:
> Hi,
> I have sent this mail once before, tell me if it's offtopic or where
> should I ask about contributing to OpenSSL.
>
> I have developed library based on OpenSSL 0.9.8 that implemented ETSI
> standard for long term signatures. It allows electr
> [EMAIL PROTECTED] - Mi. 04. Jun. 2008, 08:08:00]:
>
> We have addressed the following issue in Mac OS X:
>
> RSA_padding_check_SSLv23 has a bug in the loop that verifies the
> presence of eight consecutive 0x03 padding bytes just before the null
> marker signifying the end of the padding.
Hi,
I am new to openssl. I am trying to cross compiling openssl-0.9.8g for
linux mipsel.
I gave the following command to configure
./Configure shared no-idea no-rc5 --prefix=path to file system
linux-mipsel.
When I compile by Make command.
I am getting the error
_dl_out_of_memory @GLIBCversio
Dear,
Please find attached a patch which makes valgrind and friends happy.
Some changes had been done in md_rand.c which broke the purpose of
PURIFY. Needless to say that the define PURIFY is *not* for production
system...
Best Regards,
Frederic Heem
_
> Yep, I'll also be reverting Bodo's original idptr_callback commit too. It
Thanks for the info!
Take care,
Ger
> turns out easier to fix threadid relative to what was pre-0.9.9 than to hack
> it on top of existing stuff. So the first CRYPTO_THREADID attempt is gone,
> but I won't revert Bodo'
20 matches
Mail list logo
