Hi.
some options present in openssl utility, are not documented in manpage
(as example openssl ca -updatedb).
those options are:
req.1 - engine
req.1 - asn1-kludge
req.1 - reqopt
gendsa.1 - aes128, aes192, aes256
gendsa.1 - engine
dsa.1 - engine
dsa.1 - aes128, aes192, aes256
ca.1 - keyform
Hi!
I took 0.9.7 from OpenSSL.org and tried compiling it on Windows NT4 sp6a
with Visual Studio command line tools. I followed the instructions of
install.w32 but got the following error with ms\do_nasm:
SNIP
cl /Fotmp32dll\n_pkey.obj -Iinc32 -Itmp32dll /MD /W3 /WX /G5 /Ox
/O2 /Ob2
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
On Mon, 23 Dec 2002, Andy Polyakov wrote:
i tried this but linking the openssl program as well as the tests fails
with the following message:
cc -o openssl -DMONOLITH -I.. -I../include -DOPENSSL_THREADS
-D_REENTRANT -DDSO_DL -DOPENSSL_NO_KRB5 -DOPENSSL_NO_ASM +DA2.0 +DS2.0 +O3
On Tue, Dec 31, 2002, Wirta Ville via RT wrote:
Hi!
I took 0.9.7 from OpenSSL.org and tried compiling it on Windows NT4 sp6a
with Visual Studio command line tools. I followed the instructions of
install.w32 but got the following error with ms\do_nasm:
What version of VC++ are you
First of all it would facilitate if you could file a single problem per
report. In which the person who is considering to close the ticket won't
end up judging over things he doesn't feel like capable of judging. Like
me over your previous RT#410:-) I mean e.g. BN_sqr failure was exactly
my cup
[[EMAIL PROTECTED] - Tue Dec 31 13:21:06 2002]:
i'm having a few problems building OpenSSL 0.9.7 on a HP-UX 11.00
machine
using the HP Ansi C compiler. here's a list of the issues i've
noticed
so
far (i've listed configuration options and error messages below):
I am using
The files.
./crypto/dsa/dsagen.c
./crypto/x509v3/v3conf.c
seems no longer used (reference from makefiles). But some functions have
wrong number of arguments. The files should IMHO be removed or corrected.
Here is a patch:
-
---
The files.
./crypto/dsa/dsagen.c
./crypto/x509v3/v3conf.c
seems no longer used (reference from makefiles). But some functions have
wrong number of arguments. The files should IMHO be removed or corrected.
Here is a patch:
-
---
The ASN1_TIME_to_generalizedtime() function in openssl-0.9.7
generates a \0-terminated string instead of Z-terminated.
Problem becomes apparent when making an openssl
ocsp server and client communicate. The client
gives a OCSP_R_ERROR_IN_THISUPDATE_FIELD error.
Frederik
diff -ur
The OpenSSL-0.9.7 release is the best release I have ever seen! Works great on
Windows XP and Redhat 6.0. First time I have ever compiled on both Windows and
Linux and got NO compile errors and everything worked without having to make a
patch.
I also tested the Kerberos 5 authentication with
0.9.7-Beta4 compiled fine on this machine, 0.9.7 does not.
+ ./config --openssldir=/home/ca/OpenBSD --prefix=/home/ca/OpenBSD
Operating system: i386-whatever-openbsd
Configuring for OpenBSD-i386
IsWindows=0
CC=gcc
CFLAG =-DDSO_DLFCN -DHAVE_DLFCN_H -DOPENSSL_NO_KRB5 -DL_ENDIAN
On Tue, Dec 31, 2002 at 09:43:40AM -0800, Claus Assmann wrote:
$ make
...
(cd asm; /usr/bin/perl des-586.pl cpp dx86unix.cpp)
gcc -E -DOUT asm/dx86unix.cpp | as -o asm/dx86-out.o
des-586.s: Assembler messages:
des-586.s:2458: Error: Unimplemented segment type 135296 in parse_operand(.L009c
Some test-files include a protype for read(). Unfortunately this protype doesn't
match the one in djgpp's unistd.h. Can we not removed this prototype?
The required system headers are included already I think.
Here is a patch to make it compile for djgpp:
There was recent traffic on [EMAIL PROTECTED] about this problem. (About
3 days ago.) Using the no-asm flag clears it up. Someone said it's because
OpenBSD uses an old version of gnu as.
-f
-- Original Message --
0.9.7-Beta4 compiled fine on this machine, 0.9.7 does not.
+ ./config
This problem persists with the final release of 0.9.7 on Solaris 8,
when the code is compiled with either gcc (3.2) or Sun's C compiler
(Forte 7).
On Tue, 31 Dec 2002, OpenSSL-Bugs wrote:
Date: Tue, 31 Dec 2002 12:54:58 +0100 (MET)
From: OpenSSL-Bugs [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Arrgh nevermind. I figured out that if I do a crle and add the
directory of the library, then my problems go away. Maybe make install
could suggest this step...
---
Jeff A. Earickson, Ph.D
Senior UNIX Sysadmin and Email Guru
Information Technology Services
[[EMAIL PROTECTED] - Tue Dec 31 13:20:55 2002]:
Hi!
I took 0.9.7 from OpenSSL.org and tried compiling it on Windows NT4 sp6a
with Visual Studio command line tools. I followed the instructions of
install.w32 but got the following error with ms\do_nasm:
SNIP
cl
I am getting an error with OpenSSL 0.9.7 when trying to generate a certificate. It
appears that the uniqueIdentifier is no longer valid. Is this correct?
The following is the error:
Certificate request failed
Certification Request Failed
/usr/local/ssl/bin/openssl ca -config
[[EMAIL PROTECTED] - Tue Dec 31 13:23:43 2002]:
This patch appears to fix it (I stole the OpenBSD-sparc64 config
target). OpenSSL builds and passes 'make test'.
Looks not too bad. I'm a little worried with the following assumption, however. Can
you be sure that it doesn't hit any 32-bit
I fixed the problem, but in a different way: I changed 't-length+2' to 't-length+3'.
Please test the snapshot with name 'openssl-0.9.7-stable-SNAP-20030101.tar.gz'
whenever it appears.
This ticket is now resolved.
[[EMAIL PROTECTED] - Tue Dec 31 18:01:25 2002]:
The
21 matches
Mail list logo
