openssl-0.9.8-beta6 compiled and tested ok on the following
combinations:
- Solaris 8 SPARC cc: Sun C 5.7 2005/01/07 32-bit
(./Configure solaris-sparcv9-cc shared)
- Solaris 8 SPARC cc: Sun C 5.7 2005/01/07 64-bit
(./Configure solaris64-sparcv9-cc shared)
- Solaris 8 SPARC gcc 2.95.3 32-bit
On Jun 21 08:21, Richard Levitte - VMS Whacker wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OpenSSL version 0.9.8 Beta 6 (FINAL!)
Build and tests fine on Cygwin.
Corinna
--
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat, Inc.
Beta 6 compiles fine and passes tests on win32 (XP/VC6/nasm)
-michael
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im
Auftrag von Richard Levitte - VMS Whacker
Gesendet: Dienstag, 21. Juni 2005 08:22
An: openssl-announce@openssl.org;
Hi!
If I understood OpenSSL 0.9.8 beta 6 announcement correctly, you
wanted to see following info. Perhaps you only wanted to see test
failures reported, in that case sorry for disturbing.
Best regards,
Petri Koistinen
OpenSSL self-test report:
OpenSSL version: 0.9.8-beta6
Last change:
During installation:
installing man3/OPENSSL_Applink.3
../../util/pod2man.pl: Improper man page - no dash in NAME header in paragraph
3 of OPENSSL_Applink.pod
.3 = OPENSSL_Applink.3
installing man3/OPENSSL_ia32cap.3
../../util/pod2man.pl: Improper man page - no dash in NAME header in
On Jun 22 10:25, Corinna Vinschen wrote:
On Jun 21 08:21, Richard Levitte - VMS Whacker wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OpenSSL version 0.9.8 Beta 6 (FINAL!)
Build and tests fine on Cygwin.
Just one installation quirk. The engines are installed non-stripped
Hi,
I've tested it on the platforms below with no problems. Looking good!
Commands executed on Windows (not Cygwin):
perl Configure VC-WIN32
ms\do_ms (didn't have MASM/NASM handy)
nmake -f ms\ntdll.mak
cd out32dll
..\ms\test
Commands executed on all
On Wed, Jun 22, 2005 at 11:57:29PM +1000, Steven Reddie wrote:
Hi,
I've tested it on the platforms below with no problems. Looking good!
Commands executed on Windows (not Cygwin):
perl Configure VC-WIN32
ms\do_ms (didn't have MASM/NASM handy)
nmake -f ms\ntdll.mak
Here or on the mailing lists, I don't particularly care. Thanks for
testing!
[EMAIL PROTECTED] - Wed Jun 22 13:25:55 2005]:
Hi!
If I understood OpenSSL 0.9.8 beta 6 announcement correctly, you
wanted to see following info. Perhaps you only wanted to see test
failures reported, in that
[EMAIL PROTECTED] - Tue Jun 21 15:24:18 2005]:
I am using perl to parse result from openssl's ASN.1 and found
following problem:
Perl request ASN1_GENERALIZEDTIME to be in format 19940203T141529Z.
Openssl functrion ASN1_GENERALIZEDTIME_set does not set T between
date
and time.
[levitte - Wed Jun 22 16:31:26 2005]:
GeneralizeTime is defined in X.680 and ISO/IEC Internal Standard 8824-
1. Read carefully, it specifies that the date part should be
formatted
as specified in ISO 8601, as well as the time part, but it doesn't
say
that the combined value should be
Yep, that's the only place.
I hate DCC too...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Richard
Levitte via RT
Sent: Wednesday, June 22, 2005 5:46 PM
To: Yair Elharrar
Cc: openssl-dev@openssl.org
Subject: [openssl.org #1122] [PATCH] ssl_lib.c
No problem. I gladly defer to your experience and judgement. Thanks
for the speedy resolution. PG
__
OpenSSL Project http://www.openssl.org
Development Mailing List
Richard Levitte via RT wrote:
[levitte - Wed Jun 22 16:31:26 2005]:
GeneralizeTime is defined in X.680 and ISO/IEC Internal Standard 8824-
1. Read carefully, it specifies that the date part should be
formatted
as specified in ISO 8601, as well as the time part, but it doesn't
say
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL PROTECTED]
I sent the following on 21 June, but I don't see where it actually made
it to the list or to the archives. Sorry if it turns out to be a
duplicate.
The beta6 of openssl 0.9.8 compiles, tests, and installs on DJGPP
without any problems that I see. There is just one warning during the
compilation,
[Note: this isn't important for me as OpenBSD comes with OpenSSL,
I was just curious whether this would work.]
OpenBSD 3.2/x86:
$ ./config no-asm
Operating system: i386-whatever-openbsd
Configuring for BSD-x86
Configuring for BSD-x86
no-asm [option] OPENSSL_NO_ASM
no-gmp
OpenBSD 3.2/x86:
$ ./config no-asm
It doesn't disable asm:
This is apparently a bug in ./Configure (it's not OpenBSD specific, as
it's reproducible everywhere, shall be fixed).
dx86-out.s: Assembler messages:
dx86-out.s:2376: Error: Unimplemented segment type 135296 in
On Wed, Jun 22, 2005, Andy Polyakov wrote:
OpenBSD 3.2/x86:
$ ./config no-asm
It doesn't disable asm:
This is apparently a bug in ./Configure (it's not OpenBSD specific, as
it's reproducible everywhere, shall be fixed).
Thanks!
dx86-out.s:2376: Error: Unimplemented segment type
Here are the patches to the OpenSSL 0.9.8-beta5 Configure script for
Stratus VOS. I've tested them on a Stratus Continuum (PA-RISC) system
running VOS 14.7.0ax and on the Stratus V Series V400 system (Intel
IA32) running VOS 15.1.0ah. These changes are sufficient for our PA-
RISC platform,
These changes, together with the changes to the Configure script found
in ticket #1129, constitute the total set of changes needed to get
OpenSSL 0.9.8-beta5 to build and run its self-tests on the Stratus V
Series (Intel IA32) platform. They are not needed for the Stratus
Continuum (PA-RISC)
I've done the small amount of work to patch s_client to support explicit
AUTH TLS mode for FTPS.
Has anyone ever submitted this patch before, or should I go ahead and
send it in?
Thanks
--
Andy Steingruebl | e-mail: [EMAIL PROTECTED]
Information Security Architect| phone: (312)
I'm breaking up the changes into VOS-only changes (this patch) and a
second patch that VOS IA32 needs but which also affects other
platforms.
The second patch is contained in ticket 1130.
__
OpenSSL Project
On April 24th, I wrote to openssl-dev:
Also, the function dir_ctrl in crypto/x509/by_dir.c looks wrong to
me. Shouldn't it be checking for the environment variable first, then
getting the default if no environment variable is specified (the way
by_file_ctrl does in crypto/x509/by_file.c)?
24 matches
Mail list logo