While the USSA goverment has succeeded in FUD'ing you and preventing
the online publication of your documentatoin there is still the
possibility of publishing your doc in a useful paper form.
||ugh Daniel
[EMAIL PROTECTED]
Systems Testing
ben> OK, I propose that we follow the Apache version numbering scheme, which,
ben> I quote:
ben>
ben> /* Numeric release version identifier: MMNNFFRBB: major minor fix final
ben> beta
I assume "final" means "release"...
In any case, I like it.
ben> code until final release. I propose we do thi
Shared library support just isn't ready yet in OpenSSL. Configure and
the Makefiles need work to do it right.
Here's a completely unsupported recipe for HPUX 10.20. It assumes you
know the difference between static, static pic, and dynamic libraries.
If it doesn't work you're on your own. I'm
I'm using OpenSSL 0.9.2B and would like to enable/disable session id
caching. Is this possible from the command line, or does the software
need to be tweaked?
Thanks,
Vince
p.s. sorry if the mailing list got two copies of this. *grin* Please respond to
this one, as this is my work address
Yes. But in the context of the original message, what is meant is that
OpenSSL should not directly address the comms (send/receive).
The solution for NT using I/O Completion Ports would be to handle the
I/O in the main code and simply pass peer or application data into the
'library' and to receiv
>Since version 0.9.0b I had to use the attached patches.
>+#ifdef __STDARG_H__
>+#include
>+#else
>+#include
>+#endif
We don't support pre-ANSI C any longer. If you don't have stdarg.h,
you will have a lot of other problems.
>+++ crypto/err/err.h Fri May 14 14:23:31 1999
>+#include
Why
OK, I propose that we follow the Apache version numbering scheme, which,
I quote:
/* Numeric release version identifier: MMNNFFRBB: major minor fix final
beta
* Always increases along the same track as the source branch.
* For example, Apache 1.4.2 would be '10402100', 2.5b7 would be
'2057'
We need to increment the version number to reflect the API change in
the DES library. I don't know if the beta release is coming soon,
else I would have done it right now.
__
OpenSSL Project http://
Jon Parry-McCulloch wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> OK, for my next question:
>
> Where are they specified?
>
> Jon
They are specified in the PKIX stuff which is now RFC 2459.
The DH specified in this RFC (X9.42) isn't quite the same as OpenSSL DH
which is larg
> Ariel's documentation is very useful. Is there something more
> turorial? Something that gives more of an overview? Is there a
> reason not to include Ariel's documentation in the distribution?
One reason is that we still don't know whether or not we can include
it without violating American
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK, for my next question:
Where are they specified?
Jon
- -Original Message-
From: Ben Laurie [SMTP:[EMAIL PROTECTED]]
Sent: Monday, May 17, 1999 2:54 PM
To: [EMAIL PROTECTED]
Subject:Re: DH Cert
Jon Parry-McCulloch wrote:
>
Perhaps the simplest solution is to turn deskey into a struct whose
first element is char[8]. I think the only current code it breaks
is requiring {} around initializers and an & in key setup functions.:)
__
OpenSSL Project
> Freebsd 3.X on the alpha. Basically, it's the OpenBSD-alpha entry
If the different BSD branches use the same config, shouldn't we
use one entry (alpha-bsd, or something) for all of them?
__
OpenSSL Project
Jon Parry-McCulloch wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Chaps and Chapesses
>
> Is it my overworked imagination, or did I read here a while ago that
> someone has a draft spec for a DH certificate?
Eh? I thought they were already specified, just not very widely
suppo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chaps and Chapesses
Is it my overworked imagination, or did I read here a while ago that
someone has a draft spec for a DH certificate?
Jon
-BEGIN PGP SIGNATURE-
Version: PGPfreeware 6.0.2i
iQA/AwUBN0AaEXgWiDO86u4+EQITyQCg7mOr5hcT6oZLCXHS6
Magnus Stenman wrote:
>
> Found this in the "What's new file" for Netscape 4.6:
>
> New 56-bit DES ciphers added to both export and US versions
> (requires new SSL cipher suite server-side)
>
> What is this, and does mod_ssl (or is is OpenSSL) support it?
I added them to OpenSSL when they
Ron Ramsay wrote:
>
> We have a crypto server that uses OpenSSL as a library. (SSL *) contexts
> are given memory BIOs for I/O. OpenSSL is driven by calls to SSL_read(),
> SSL_write(), BIO_read() and BIO_write(). There are no sockets.
>
> I am attaching an archive containing the source code that
IO Completion Ports are a NT specific feature, used with non-blocking IO (also
called asynchronous IO or overlapped IO in NT terminology). If a socket is
registered with a completion port, a completion packet will be queued with the
port when a non-blocking IO operation completes. One can then fet
[EMAIL PROTECTED] wrote:
>
> can anyone give me direction on how to compile openssl as a shared library
> instead of an archive on HPUX or Linux?
>
> thanks,
> son
>
Unless it broke during the last changes, on the current snapshot
version,
on a linux (well, gcc/binutils) installation:
./confi
19 matches
Mail list logo
