> file crypto/cryptlib.o
> crypto/cryptlib.o: ELF 32-bit MSB relocatable SPARC32PLUS Version 1, V8+
>Required, UltraSPARC1 Extensions Required
Looks great!
>
> thus when I do use "nm" to list the archive library created:
>
> nm -u libcrypto.a
> nm: cryptlib.o: File format not recognized
>
> 1) I note there is an edian flag but I do not understand at this point
> why it is present. It is quite trivial for the software to determine
> the edian order of a CPU and to my way of thinking the user/installer
> should not be asked for information
You're not actually asked for it and moreov
On Fri, Sep 24, 1999 at 10:05:28AM -0400, Jim Miller wrote:
> Anyone had any problems with a browser trying to connect to an OpenSSL
> server? I seem to be getting upset down in the code because of a
> version conflict.
>
> Call trace:
>
> mycode()
> SSL_accept()
> ssl3_accept()
>
> enc_writ.c:159: `EINTR' undeclared (first use this function)
> ...
> Operating system: i686-whatever-linux2
> ...
double-check if you have /usr/include/asm. it's normally a symbolic link
pointing at include/asm-i386 in kernel source tree. andy.
___
Any help would be appreciated in determining the error referenced below.
This is when running the initial make.
gcc -I.. -I../../include -DTHREADS -D_REENTRANT -DL_ENDIAN -DTERMIO -O3
-fomit-f
rame-pointer -m486 -Wall -DSHA1_ASM -DMD5_ASM -DRMD160_ASM -c enc_writ.c
-o en
c_writ.o
enc_writ.c: In
Hi users,
I am looking to build a prototype for my application using OpenSSL. I have
downloaded the OpenSSL Tool Kit and installed it. I am desperately looking for
examples, demos programs with source, so that i could quickly jump-start my
prototype development in Win NT4.0. If
Anyone had any problems with a browser trying to connect to an OpenSSL
server? I seem to be getting upset down in the code because of a
version conflict.
Call trace:
mycode()
SSL_accept()
ssl3_accept()
ssl3_get_message()
ssl3_read_bytes()
ssl3_get_record()
{
p = s->packet; // my
How do I submit bug reports? I couldn't find anything at www.openssl.com,
but maybe I'm missing something obvious. I have some more bug reports to
submit.
I'm using v0.9.4.
Minor bug (found by purify, but unlikely to really cause problems on
most architectures) in BN_bn2hex():
< buf=(char
OpenSSL 0.9.4
There's a typo in an error message in apps/speed.c:
--- speed.c.org Wed Sep 22 09:53:52 1999
+++ speed.c.fix Wed Sep 22 10:14:21 1999
@@ -997,7 +997,7 @@
RSA_PKCS1_PADDING);
if (rsa_num2 <= 0)
{
The list of client ciphers displayed by s_server gets truncated at 32 bytes
because bufsize is too small. The BUFSIZZ value used in the other apps is
defined in s_server.c but it's ignored. It looks like it has been this way
forever. No one else ever noticed?
Index: apps/s_server.c
===
I decided to just pick apart the RSA key and stuff it manually into the
OpenSSL RSA key structure.. Things work fine now.
Thanks.
-Jim
Dr Stephen Henson wrote:
> Jim Miller wrote:
> >
> > I am working on adapting our PKI toolkit to use OpenSSL. We of course
> > have our own internal format for
1) I note there is an edian flag but I do not understand at this point why it is
present. It is quite trivial for the software to determine
the edian order of a CPU and to my way of thinking the user/installer should not be
asked for information that the software can
detect for itself at run
12 matches
Mail list logo