On Tue, Feb 05, 2002 at 06:42:08PM -0600, Wendy Palm wrote:
--- config.orig Mon Feb 4 16:12:43 2002
+++ config Tue Feb 5 16:01:09 2002
@@ -302,6 +302,13 @@
echo ${MACHINE}-whatever-cygwin32; exit 0
;;
+*CRAY T3E)
+ echo cray-t3e; exit 0;
+ ;;
+
On Thu, Feb 21, 2002 at 10:34:47AM +0100, Oscar Jacobsson wrote:
* The fix for crypto/tmdiff.c (ie. the diff between 1.9.2.1 1.9.2.2)
needs to be merged into this branch as well. Missing #endif.
Fixed.
* crypto/bio/bss_bio.c now checks SSIZE_MAX, and in the visual c++
limits.h this won't
On Thu, Feb 28, 2002 at 09:11:54AM +0100, Joerg Voelker wrote:
if I try to compile openssl 0.9.7 under win2k with mingw32 I get the
following error:
ranlib out/libssl.a
gcc -o
tmp/md2test.o -Ioutinc -Itmp -DL_ENDIAN -DDSO_WIN32 -fomit-frame-pointer -O3
-m486 -Wall -DBN_ASM -DMD5_ASM
On Wed, Feb 27, 2002 at 11:39:26PM +, Tom Cosgrove wrote:
There's a problem in bntest.c from openssl-0.9.6c. It appears that
this revision of the file is still the latest (rev 1.55), at least
via CVSweb.
The problem is that there are calls to BN_free() to attempt to free
BIGNUMs that
On Wed, Feb 20, 2002 at 09:59:19AM -0800, Leonard Janke wrote:
According to PKCS #9 v2 gender should have the OID
1 3 6 1 5 5 7 9 3
and psuedonym should have the OID
1 2 840 113549 1 9 3.
According to OpenSSL's objects.h gender has the OID
1 3 6 1 5 5 7 9 4
and pseudonym has
Thanks for the clarification. Mea culpa. It turns out I was
looking at bntest.c from OpenSSL and bn_lib.c from an old SSLeay
version.
(The background is that I have been brought into a project that
uses some of the BN code, and I wanted to add test suites. So
I brought in the OpenSSL bntest.c
Hello,
I have a simple client/server application based on OpenSSL (0.9.6c).
The server runs on SuSE Linux, the client on Win98.
I built the OpenSSL DLLs on my Windows system and tested the
client application. It was OK.
Then I copied these DLLs to a different Win98 system, run the client
and
Bodo Moeller wrote:
* crypto/bio/bss_bio.c now checks SSIZE_MAX, and in the visual c++
limits.h this won't get defined unless one defines _POSIX_. Should this
definition go into e_os.h or is it ok to simply insert it here prior to
the inclusion of limits.h?
If SSIZE_MAX is not defined,
Bodo Moeller wrote:
On Tue, Feb 05, 2002 at 06:42:08PM -0600, Wendy Palm wrote:
--- config.orig Mon Feb 4 16:12:43 2002
+++ config Tue Feb 5 16:01:09 2002
@@ -302,6 +302,13 @@
echo ${MACHINE}-whatever-cygwin32; exit 0
;;
+*CRAY T3E)
+ echo
On Fri, Mar 01, 2002 at 06:36:59PM +0100, Oscar Jacobsson wrote:
Sorry for not being clearer. The reason I (or my compiler rather) was
worrying about it is that it's actually a case of _INT_MAX being used
rather than INT_MAX.
Oh, that. I think that was a typo; all the other branches use
10 matches
Mail list logo
