Lennart Bång [EMAIL PROTECTED]:
Here is the openssl apps patch though to fix the problems I
have found with the apps only capable of running once
(when running and never exiting) due to global variables.
The patch could maybe also fix probs with running apps
repeatedly from the openssl
Mark Carey-Smith [EMAIL PROTECTED]:
I'm currently trying to build an openssl 0.9.4 distribution which fails on
the make install step after the previous steps all work correctly.
./configure --prefix=/citec/openssl-0.9.4
./make
./make test
./make install
make install output:
[...]
***
Chris Zimman [EMAIL PROTECTED]:
Bodo Moeller:
[...] maybe in an ideal world it'd be possible to request that slow
software bignum operations be "non-blocking" too in the sense that
after doing some of their work they'd return control to the
top-level, which then can handle oth
Lennart Bång [EMAIL PROTECTED]:
I am in the process of porting all the apps/*.c to target
in order to get the whole 'openssl' program running
on OSE RTOS on a powerpc.
The problem is that the programs use global variables
and does not bother to clear them and the simple
shell I am using
Dr Stephen Henson [EMAIL PROTECTED]:
[...] I think the idea of forcing people to use threads to obtain
decent performance is unacceptable. [...]
Quite a few applications already follow the "one SSL connection per
thread or process" model.
One reason for doing things that way (threads
David Taylor [EMAIL PROTECTED] to [EMAIL PROTECTED]:
[...]
We have added TLS 1.0 support but it is still in testing.
A question about the TLS protocol. The specification states the client key
exchange message should send the same version number that was included in
the client hello - the
Jeremy Poulter [EMAIL PROTECTED]:
To further my earlier message, I have just done a succesful compalation and
test on a Debian based machine. The machine that produced the error was a
Redhat 5.2 based machine. The test also now works on the Redhat machine
(using the library produced on the
Torsten T. Fokuhl [EMAIL PROTECTED]:
BSDI 4.x has changed to ELF format,
configure failed on bsdi box, tried to use old bsdi.
[...]
/usr/local/archive/compile/openssl-0.9.3a
^^
That's an obsolete OpenSSL version (and you almost managed not to
mention
Dan O'Reilly [EMAIL PROTECTED]:
Sorry to break in, but is there a need for a guy who can do development
for VMS on OpenSSL...?
Richard Levitte prepared the VMS support. You are apparently in the
US, which means that the EAR (recently renewed because of a continuing
"national emergency", see
On Tue, Aug 10, 1999 at 03:30:14PM -0400, Sean Han wrote:
I got some error messages while compiling the openssl-0.9.3a. Here are the
error messages:
gcc -I.. -I../../include -DTERMIOS -D_ANSI_SOURCE -O3 -fomit-frame-pointer -
m486 -Wall -c read_pwd.c
read_pwd.c: In function `des_read_pw':
On Tue, Aug 10, 1999 at 10:54:11AM -0700, Curtis Wood wrote:
I'm writing a fancy networking deal that could use some encryption stuff
- the only problem is that I need it to be thread safe... Does openssl
cover this?
Yes.
Stefan Kelm [EMAIL PROTECTED]:
make: Fatal error: Don't know how to make target `asm/md5-sparcv8plus-gcc27.o'
Oops. Either upgrade to gcc 2.8.x :-), or add an "a" in line 80 of
crypto/md5/Makefile.ssl.
__
OpenSSL Project
Lidong Zhou [EMAIL PROTECTED]:
BUG1:
Symptom: If we run the provided s_server and s_client (in the apps
directory) under the default SSL version, the client will wait for
more inputs after receiving a renegotiation request from the server
(sent by s_server when we enter "R" from stdin). If
On Wed, Aug 11, 1999 at 08:15:03AM -0500, Charles D. Fultz wrote:
I do have librsaref.a in my lib path. I've successfully compiled OpenSSL
on Sparcs running Solaris 2.5.1 and 2.6. But, I haved recieved the error
below when compiling on x86's running both 2.5.1 and 2.6.
What does "nm
On Wed, Aug 11, 1999 at 11:54:03AM +0100, Dr Stephen Henson wrote:
[...]
The easiest solution is to make the perl script take its input from a
file and write to a file, then you should be able to use '/' for
everything. So it would be called as
system("perl xxx.pl path/to/in path/to/out");
On Mon, Aug 09, 1999 at 10:48:54AM -0400, Vincent Levesque wrote:
[...]
The ssl handshake is not initiated until a BIO_read or a BIO_write to the
SSL end of the filter. In order to force the initialization of the
handshake without actually exchanging data it is possible to call those
On Mon, Aug 09, 1999 at 06:41:57PM +0200, Ulf Möller wrote:
This script tries to figure out which compiler is installed, then
configures and compiles OpenSSL. (Tested with Mingw32 only.) Comments?
# ms/config.pl
^^
[...]
print "\nDone compiling OpenSSL.\n";
Ralf S. Engelschall [EMAIL PROTECTED]:
Any objections for the following last-minute patch which tries to fix the
problems the RSAref-users had (they need libRSAglue.a installed)?
Index: rsaref/Makefile.ssl
===
RCS file:
On Thu, Aug 05, 1999 at 05:38:28PM -0300, Juan Carlos Castro y Castro wrote:
[...]
The two first commands work ok; when I try the third one I get this:
making all in crypto...
make[1]: Entering directory `/home/jcastro/openssl/work/crypto'
make[1]: *** No rule to make target `all'. Stop.
On Mon, Jul 12, 1999 at 12:00:00AM +, Dr Stephen Henson wrote:
Bodo Moeller wrote:
Is there a canonical way to extend the ASN.1 that we have for DH to
allow including optional subprimes?
Well I don't know about "canonical". Several of the ASN1 structures used
(e.g. DSA pr
You wrote:
I tried compiling openssl 0.9.3a. I got a error doing the 'make'. I did try
doing the config with 'no-asm' option, but this did not make a difference. I
have encluded the error and config -t as requested.
gcc -I.. -I../../include -DTHREADS -D_REENTRANT -O3 -fomit-frame-pointer
I am able to do this with ssleay:
ssleay.exe enc -des -in input.txt -out output.txt -e -a -k mypassword
[...] for "openssl enc", you could use, say,
-des_ede instead of -des. (-des_ede is two-key Triple-DES).
Look at its implementation (apps/enc.c) to see what
On Tue, Aug 03, 1999 at 12:07:54PM +0200, Alberto Velo wrote:
now I'd like to do a simple application, which gets an ascii input file and
creates an encrypted (DES) output file.
I am able to do this with ssleay:
ssleay.exe enc -des -in input.txt -out output.txt -e -a -k mypassword
I
Any thoughts regarding changing things such as (and this is just purely an example):
#define d2i_X509_fp(fp,x509) (X509 *)ASN1_d2i_fp((char *(*)())X509_new, \
(char *(*)())d2i_X509, (fp),(unsigned char **)(x509))
to use typedef'd callbacks, that are extern "C" under C++?
Juan Carlos Castro y Castro [EMAIL PROTECTED]:
3) The output of the previous command is in makedepend.out.gz. I got
lots of warnings about cipher.h missing, but the first one is about
some "buildinf.h" which worries me.
crypto/buildinf.h does not exist at that stage ... this should help
On Tue, Aug 03, 1999 at 03:50:01PM +0400, CyberPsychotic wrote:
[openssl people: sorry for crosspost, I just hope you could have something
to add to our discussion. We basically talk about the problem with compiling
openssl+apache+mod_perl. Since crypto/des/des.h file defines _ as ks._ (if
Juan Carlos Castro y Castro [EMAIL PROTECTED]:
I'm in sync with the CVS tree. I'm trying to compile OpenSSL with
./configure no-asm no-dh no-bf no-many other ciphers
make[2]: *** No rule to make target `../../include/openssl/dh.h', needed by
`rsa_sign.o'. Stop.
make[2]: Leaving
On Fri, Jul 30, 1999 at 12:23:00AM +0200, Bodo Moeller wrote:
From: Vincent Levesque [EMAIL PROTECTED]:
I'm using a bio pair combined with an ssl_f_bio, [...]
[...] SSL_ERROR_WANT_READ [...] SSL_ERROR_WANT_WRITE [...]
As you said that you're using BIO_f_ssl (modulo case and sorting
From: Vincent Levesque [EMAIL PROTECTED]:
I'm using a bio pair combined with an ssl_f_bio, just as in
/test/ssltest.c in the recent snapshots. I'm looking for a way to do a
select() or something similar on the bio pair. I looked around and I
didn't find much information about that or about
Dmitry Solodovnick [EMAIL PROTECTED]:
I tried to test my sever application (based on OpenSSL-0.9.3a library)
on Windows NT (it worked correctly on Solaris 2.7 and Linux RH without
memory leaks etc.).
But on NT I got an error after 2- 4 hours working in hard mode ( after
~~ 1500 HTTP
gic [EMAIL PROTECTED]:
I was developing an SSL client (with openssl-0.9.3a)
and found memory leaks when using RC4-MD5 (1024/128 bits).
HOWEVER, when I switched to "EXP-RC4-MD5" (512/40 bits),
there are NO leaks.
The best way to reproduce the leaks is to run 's_time'
for a long time. (Use
As recently problems have been reported on a Solaris system with the
CFLAGS= $(INCLUDE) $(CFLAG) -DCFLAGS="\"$(CC) $(CFLAG)\"" -DPLATFORM="\"$(PLATFORM)\""
definition in crypto/Makefile.ssl (which is there so that
crypto/cversion.c can return meaningful answers to
SSLeay_version(SSLEAY_CFLAGS)
[EMAIL PROTECTED] (Ulf Möller):
without any problems with newly compiled shared libraries: The new
library functions will expect one parameter that is not actually there
and will take whatever happens to be on the stack and pass it to the
Although you are likely to get away with this, it
On Tue, Jul 20, 1999 at 10:55:20AM +0100, Ben Laurie wrote:
Bodo Moeller:
So, is backwards compatibility an important issue here
and is it worth this kind of evil hack, or should we
just add the parameters?
Backward compatibility is an important issue. Think "dynamic
li
Timothy Canfield [EMAIL PROTECTED]:
I have noticed that much of the overhead of an openssl session is during
the connection stage. Is it possible for me to use only one SSL_session
for every connection that which I accept. This will make it easier to
crack a session, right? Will it also
Is there any particular reason why mk1mf.pl couldn't pick up the
CFLAG definition from the top Makefile, so that they'd all be in
Configure rather than in separate Perl files in the util/pl directory?
__
OpenSSL Project
On Mon, Jul 12, 1999 at 10:16:50PM -0400, Timothy Canfield wrote:
I'm trying to find out the proper thing to do, when either SSL_read or
SSL_write return SSL_ERROR_WANT_READ.
See the archives of this mailing list of about a week ago,
thread "SSL_ERROR_*".
[EMAIL PROTECTED] (William M. Perry):
Any reason the dependencies aren't auto-generated?
They are!
I do not mean by the developers - I mean stripping them out of the
distribution and let the generation of dependencies be part of the
configuration or standard make process.
For some time
On Fri, Jul 09, 1999 at 09:27:33AM -0500, William M. Perry wrote:
Note in particular this line:
checking which DES optimizations to use... -DDES_RISC2 -DDES_PTR
Nice, but in some cases it is better to actually know what you are doing
than just pick some flags and try if it appears to
On Wed, Jul 07, 1999 at 10:24:22AM +0200, Juan Pablo Rojas Jimenez wrote:
Bodo Moeller wrote:
SSL_ERROR_WANT_WRITE
SSL_ERROR_WANT_READ
These can happen only with non-blocking I/O (or with BIO pairs, which
will be available in OpenSSL 0.9.4). It means that the program has to
retry
On Wed, Jul 07, 1999 at 10:26:18AM +0200, Juan Pablo Rojas Jimenez wrote:
Bodo Moeller wrote:
When discussing the semantics of SSL_read etc., SSL_pending should
also be mentioned, I guess, although I currently can't think of any
scenario where you'd really *need* it. SSL_pending tells you
On Tue, Jul 06, 1999 at 01:50:31PM +0200, Bodo Moeller wrote:
On Tue, Jul 06, 1999 at 11:16:50AM +0200, Juan Pablo Rojas Jimenez wrote:
Could anyone tell me what's the exact meaning of the possible errors
returned in a SSL_read/write call.
[...]
When discussing the semantics
On Tue, Jul 06, 1999 at 11:16:50AM +0200, Juan Pablo Rojas Jimenez wrote:
Could anyone tell me what's the exact meaning of the possible errors
returned in a SSL_read/write call.
Note that those errors are not returned by
SSL_{accept,connect,read,write}, but are returned by
On Fri, Jul 02, 1999 at 11:04:47AM +0200, Andy Polyakov wrote:
My Sparc 10 with solaris 2.6 fails to compile openssl. I have included
output from the "config -t" command and from make.
I bet you've upgraded OS, but never run fixincludes script. Consult
READMEs in gcc source code tree *or*
On Fri, Jul 02, 1999 at 11:39:28AM +0200, Andy Polyakov wrote:
As a matter of fact I don't see any
strong reason to compile 64-bit applications except when I have to
address matrices larger than 2GB.
Occasionally one has to handle 2GB of data, and it's hardly
Michael Bai [EMAIL PROTECTED]:
There is a way to change SSL chipher list in openssl
SSL_CTX_set_cipher_list(ssl_ctx, char * )
But I can not figure out the rule of chipher string.
Section ssl-ciph.doc in doc/ssleay.txt has an explanation,
SSL_DEFAULT_CIPHER_LIST in ssl/ssl.h is an example,
On Mon, Jun 28, 1999 at 01:12:35PM +0100, Chad C. Mulligan wrote:
My Quivering Choad tells me that Bodo Moeller had this to say:
On Thu, Jun 24, 1999 at 02:34:03PM +0100, Chad C. Mulligan wrote:
I've noticed that there is a memory leak in dsa_sign.c
The BN* kinv is not being freed before
[EMAIL PROTECTED] (William M. Perry):
You should definitely check whether either cc or gcc can actually
generate an executable before choosing it. Although this would
break cross-compiling... hmmm
When cross-compiling, you obviously wouldn't use ./config anyway.
On Thu, Jun 24, 1999 at 02:34:03PM +0100, Chad C. Mulligan wrote:
I've noticed that there is a memory leak in dsa_sign.c
The BN* kinv is not being freed before the function exits;
Thanks for pointing this out. After verifying that fix I found
another memory hole, and noticed that the
On Fri, Jun 25, 1999 at 04:36:06PM +0200, Holger Reif wrote:
Bodo Moeller schrieb:
[...] noticed that the openssl.c application did
not really enable memory hole checks (CRYPTO_MEM_CHECK_ON should be
..._ENABLE) -- does anyone know what reason this could have?
Seems you
On Wed, Jun 23, 1999 at 08:02:28AM +0200, Arne Ansper wrote:
Bodo Moeller:
It will work with the current implementation (but only if the
applications don't do too stupid things, such as point to a buffer
with different contents); but this may change.
if the application does stupid things
On Wed, Jun 23, 1999 at 11:17:26AM +1000, Zik Saleeba wrote:
When attempting to compile OpenSSL 0.9.3a on solaris x86 2.6 I found
that compilation failed in crypto/sha/sha_dgst.c with the following
error:
[...]
Assembler: sha_dgst.c
aline 425 : Illegal mnemonic
aline
On Thu, Jun 10, 1999 at 02:13:51PM +0200, Sherry Davar wrote:
make[1]: ar: Command not found
# ./config -t
Operating system: sun4d-sun-solaris2
Configuring for solaris-sparc-gcc
/usr/local/bin//perl ./Configure solaris-sparc-gcc
# PATH=/usr/ccs/bin:PATH
# make
On Thu, Jun 10, 1999 at 12:31:16PM -0400, John R Levine wrote:
BSD/OS 4.0 uses ELF objects and the ELF-compatible assembler. The options
for FreeBSD-ELF work OK for BSD/OS 4, so here are tweaks to the 0.9.3a config
and Configure.
I added such a configuration some days after 0.9.3a was
On Wed, Jun 09, 1999 at 11:36:50AM -0400, Titchener, Tom wrote:
In s3_pkt.c, there is a function called ssl3_write_bytes(). In that
function, there is a statement :
s-handshake_func(s)
If the server is suddenly shutdown when the client is writing bytes to the
server, this statement
On Mon, Jun 07, 1999 at 05:52:24PM +0200, Goetz Babin-Ebell wrote:
I think in b_sock.c I've stumbled into some error cases in which some locking
isn't undone:
It's wrong anyway, I haven't come around to change it ...
That caching gethostbyname function is only suitable for
single-threaded use
Goetz Babin-Ebell [EMAIL PROTECTED]:
I think in b_sock.c I've stumbled into some error cases in which some locking
isn't undone:
- if (ret == NULL) return(NULL);
+ if (ret == NULL)
+ goto err;
- if (ret == NULL) return(NULL);
- if (j
On Mon, Jun 07, 1999 at 11:54:43PM +0200, Andy Polyakov wrote:
When building openssl-0.9.3 on HP-UX 9.07 with the HP-UX native
unbundled cc, exptest dies [...]
Did the IRIX bug fix break this,
I find it hard to beleive.
[...]
Now the real problem:-) Being HP-UX illiterate (well, when it
On Tue, Jun 08, 1999 at 01:12:00AM +0200, Bodo Moeller wrote:
The exception that was reported in the message starting this thread
was in line 98 of bn_asm.c, according to the backtrace provided in
that message; but the compiler options did not include BN_LLONG,
Er, wrong. It's
On Tue, Jun 01, 1999 at 11:17:32PM -0400, Rich Salz wrote:
Well, the authorityKeyIdentifier (consisting presumably just of a
KeyIdentifier) would have to match the issuer's subjectKeyIdentifier;
why would we care how that has been computed?
Because the CA might not put the AKI in certs that
Craig Carey [EMAIL PROTECTED]:
The Perl script "Configure" contains the line:
system "perl crypto/objects/obj_dat.pl crypto/objects/objects.h
crypto/objects/obj_dat.h";
What's wrong about that line? The Perl pointed to in INSTALL.W32
doesn't seem to have any problems with it (other
While it is true that the maximum TLS record size is 16k, this doea not
relate directly to the TCP handling.
For example, the server hello, certificate request, etc are individual
records but they are all bundled into the one TCP record because it is
(apparently) more efficient to perform
On Sat, May 29, 1999 at 02:08:00PM +0200, Andy Polyakov wrote:
P.S. Common comment about this list. Or rather the way the list software
is configured. I've answered another question (about Solaris 7 x86)
yesterday. After I sent my reply away, I've realized that it won't rich
the person who
Rich Salz [EMAIL PROTECTED]:
OpenSSL currently thinks that the DN can be used as a primary key for
certificates
Yeah, that's way too simple-minded.
One first step to make things right is to use the DN
plus any key identifier that may be available
The nice thing about key (and/or cert)
and found the "fgets(tty): Invalid argument" was
caused by the following code in crypto/des/read_pwd.c
#ifdef DEBUG
perror("fgets(tty)");
#endif
The argument of fgets should be [...]
"fgets(tty)" is just a string there; if anything is wrong, then it
might be that perror has not
Stefan Kelm [EMAIL PROTECTED]:
I have realized that a root-cert that was generates via req -x509...
always gets the serial-number "00". I think this could lead to some
trouble if you want to renew the root-cert (for whatever reason) with
the same subject name. So it would be good idea to use
So should all occurrences of SHA_ASM just be changed to SHA1_ASM for
consistency (or, for even more consistency, all occurrences of
SHA1_ASM to SHA_ASM)?
I vote for more consistency. :)
It wouldn't really result in any consistency because, while there's an
assembler implementation of
"Gang Lu" [EMAIL PROTECTED]:
Recently, I built a simple client/server program when trying
openssl-0.9.2b. However, when I try to send 64K bytes from client to
server, I found that server has to get those data by 4 times usingh
SSL_read. That means I use SSL_read 4 times to get all 64K data
I've installed GNU binutils which contains the GNU assembler and
everything compiled fine.
Sorry for the false bug report.
I wouldn't call it false. On Sparcs, it's the other way around --
you can't compile various files with GNU as, you need the system
assembler.
On Wed, May 26, 1999 at 12:30:23PM +0200, Rainer W. Gerling wrote:
Compiling 0.9.3 under NT4/egcs-1.1.2 including the test went fine
after I changed line 6 in util/pl/mingw32f.pl to read
$o='/';
that is one slash insteat of two backslash.
Presumably you should have used util/pl/Mingw32.pl
On Wed, May 26, 1999 at 09:59:54AM -0400, Salz, Rich wrote:
It's much less confusing to have the header files in the same
directory as the corresponding source code than cramming all 50 of
them into a single directory.
Seems to me the difference is "rc4.h" or "../include/rc4.h"
when
"Gang Lu" [EMAIL PROTECTED]:
I tried to build a client and a server based on the example of cli.cpp
and serv.cpp in openssl-0.9.2b. However, I always get the following erro
message:
19296:error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared
cipher:S3_srvr.c:759
Could anyone give
On Mon, May 24, 1999 at 10:15:22AM +0200, Richard Levitte - VMS Whacker wrote:
Please ignore the previous diff I sent, and use the following
instead.
[...]
--- VMS/openssl_utils.com 1999/05/17 12:06:06 1.1.1.1
+++ VMS/openssl_utils.com 1999/05/23 19:37:28
@@ -24,6 +24,7 @@
$
On Thu, May 20, 1999 at 01:26:37PM +0200, Ralf S. Engelschall wrote:
#define OPENSSL_VERSION_DATE 0x19990518
Yes, an automatic and simple approach like this is ok.
Can you add something like that (with proper CVS check-in) to the
script that creates the tar's?
You want to check it in for
On Thu, May 20, 1999 at 01:22:33PM +0100, Seán ó Ríordáin wrote:
but now in crypto/md5... when compiling md5_dgst.c I get...
make[2]: Entering directory
`/export/home/sean/crypto/openssl-work/crypto/md5'
gcc -I.. -I../../include -DTHREADS -D_REENTRANT -O3 -fomit-frame-pointer
-mv8 -Wall
Bodo Moeller [EMAIL PROTECTED]:
Richard Levitte:
If e_os.h shouldn't be exported, shouldn't it be removed from the
EXHEADER macro in Makefile.org?
In theory, yes. [...] apparently no-one felt like doing that up to
now :-)
Proposal: Make a symlink to e_os.h in each directory where
"Ralf S. Engelschall" [EMAIL PROTECTED]:
Yes, Ben is right: At the release level people can use OPENSSL_VERSION_NUMBER
and that should be enough. When we start at the development level to increase
a number for every API change we get the same chaos as for Apache: it's often
forgotten, people
But anyway I think that it shouldn't be necessary to use a verify
callback function. I've recently added functions to the SSL API that
allow defining a verification depth, because this is something that
the library should be able to do, and there _is_ support for it in the
X.509 library
On Wed, May 19, 1999 at 09:39:36AM +0100, Seán ó Ríordáin wrote:
In the Change log for gcc 2.8.0 there is an entry for "Mon Oct 20
17:29:55 1997" where Doug Evans added the ultrasparc case. At
ftp://ftp.gnu.org/pub/gnu/gcc/, the file gcc-2.9.0.tar.gz is dated "Wed
Jan 14 00:00:00 1998"
Andy Polyakov [EMAIL PROTECTED]:
(I've added a new entry
solaris-usparc-oldgcc for this which is the same as solaris-usparc-gcc
except that -mcpu=ultrasparc is not set.
Wow-wow-wow! The least you could do is to say -mv8 instead:-)
Er, yes. I've added -mv8 now.
On Tue, May 18, 1999 at 05:19:01PM +0200, Ulf Möller wrote:
#if OPENSSL_VERSION = 0x00904000
In that case I would just test for the release version number
OPENSSL_VERSION = 0x000904100, ignoring that the feature already is
present in some of the development versions.
But we're talking
On Sat, May 15, 1999 at 06:12:25PM -0400, D. Hugh Redelmeier wrote:
| From: Bodo Moeller [EMAIL PROTECTED]
| Reply-To: [EMAIL PROTECTED]
| Subject: (const) des_ctype
|
| I have prepared a set of patches to the DES library that should solve
| the const problem.
Pluto currently uses
On Sun, May 16, 1999 at 09:04:28AM -0400, Dave Clark wrote:
I'm also a newbie who's interested in finding the most recent
OpenSSL documentation, particularly the X509[v3] component.
Where is "Ariel's documentation?"
At URL:http://www.columbia.edu/~ariel/ssleay/ (see "Related" area at
On Thu, May 13, 1999 at 10:42:39PM -0700, Mixmaster wrote:
Speaking of threads and the freeze, is the patch to put locks around
thread unsafe functions going to be put in?
Done.
And someone needs to dig up the canonical list of all unsafe functions
and check to see if there are others used
On Fri, May 14, 1999 at 04:20:49PM +0200, Roger Bodén wrote:
We have an application on Windows NT that uses IO Completion ports for
its socket communication. I now need to add SSL support to secure this
communication and we are considering using openssl for this.
I had a look at header
On Mon, May 10, 1999 at 04:30:02PM +0200, Bodo Moeller wrote:
On Mon, May 10, 1999 at 03:21:05PM +0200, Ralf S. Engelschall wrote:
How much time do you need for
incorporating your changes? When you can finish it the next two or
three days, it should
When on a solaris-usparc-gcc system "as" is GNU-as and not the system as
(which can happen if the directory containing all the GNU tools occurs
early in the PATH -- can we at least rely on the real "as" being
available on all systems?), you get lots of error messages:
gcc -E asm/sparcv8plus.S |
Ron Ramsay [EMAIL PROTECTED]:
[...]
The global variable verify_error does nothing in the example code. It
could be used for communicating with the main-line but this is not
shown. Surely it would be better to jettison this variable and to put
your own error on ctx-error. In particular, the
On Mon, May 10, 1999 at 09:47:41AM +0200, Ralf S. Engelschall wrote:
Friends, please let us remind now that we proposed the code freeze
for OpenSSL 0.9.3 for today (see STATUS document)
Readers of openssl-cvs of course know that the STATUS document itself
does not quite follow the freeze
On Sat, May 08, 1999 at 01:19:14PM +0100, Ben Laurie wrote:
Bodo Moeller wrote:
But the problem is in the system header files, not in the program.
When those header files are not quite as they should be, warnings can
be inevitable (on Linux, you cannot compile programs that #include
sys
Ben Laurie [EMAIL PROTECTED]:
I guess we start with your suggestion above and see what kind of mess we
have left afterwards?
O.K., I have now started: SSL_new now copies ctx-cert (formerly known
as ctx-default_cert, but now it is no more a default than various
other members of SSL_CTX that
On Sun, May 09, 1999 at 10:12:00PM +0200, Bodo Moeller wrote:
O.K., I have now started: SSL_new now copies ctx-cert (formerly known
as ctx-default_cert, but now it is no more a default than various
other members of SSL_CTX that have always been copied during SSL_new),
and s-ctx-[default_
Sebastian Akerman [EMAIL PROTECTED]:
crypt/evp/bio_enc.c: static int enc_read(b,out,outl)
/* Should be continue next time we are called? */
if (!BIO_should_retry(b-next_bio))
{
ctx-cont=i;
i=EVP_CipherFinal((ctx-cipher),
(unsigned char *)ctx-buf,
Niels Poppe [EMAIL PROTECTED]:
Bodo Moeller:
David Harris:
My original request was for something slightly different, I think.
[...] I want to run "make" and have
all the programs compiled _as-if_ they would be installed into the
/usr/loca
On Fri, Apr 30, 1999 at 01:06:35PM +0200, Martin Kraemer wrote:
The Rev. 1.65 patch broke Configure. 1.64 was okay.
I'd fixed that one five secondes before reading your e-mail message ...
I've also changed mklink.pl to use
my $dirname;
foreach $dirname (@) {
...
},
I hope your version
On Wed, Apr 28, 1999 at 12:27:49PM +0200, Niels Poppe wrote:
Ulrich Drepper wrote:
[EMAIL PROTECTED] (Bodo Moeller) writes:
Turns out that the Linux-specific parts of glibc 2.1 doesn't pay
attention to the standards in the first place and _always_ defines
errno to be that macro. So, unless
From the current STATUS file:
o Install prefix for packagers ([EMAIL PROTECTED])
o The installation under "make install" produces a very
installation layout: $prefix/certs and $prefix/private dirs. That's
not nice. [...]
Paul: why is it not nice?
On Tue, Apr 27, 1999 at 11:18:20AM -0400, Tom Titchener wrote:
Finding the #ifndef WINDOWS in apps/s_client.c prevented me from
using the otherwise-oh-so-complete feature set of this application
on my OS 'of choice'
Well, also in the "apps" directory there's a file sc.c that purports
to be a
"Titchener, Tom" [EMAIL PROTECTED]:
Well, also in the "apps" directory there's a file sc.c that purports
to be a version of s_client.c that has been doctored for Windows.
Some time ago, I asked if anyone saw any value in integrating it into
s_client.c.
Yes. With one minor change (add
On Sun, Apr 25, 1999 at 02:38:48PM +0200, Ralf S. Engelschall wrote:
I think we should by default define _REENTRANT or _THREAD_SAFE or any
other system-dependent macros that are needed to get a library that
can be used in multi-threaded programs. (This means, for example,
that errno is not
501 - 600 of 636 matches
Mail list logo
