How can I get current time inside Apache-OpenSSL (in ssl_engine_kernel.c)
and also sum a value in time format ?
Thanks everybody
Andrea
__
OpenSSL Project http://www.openssl.org
Development
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"
I'd picked up gcc 2.7.2.3 because it was all that I saw on
Ulf Möller wrote:
release without change if they track all the way to the end. We don't
support distinguishing an arbitrary snapshot of a development version,
though; only the latest. So, if you have support for a feature in 0.9.4,
then you test like this:
#if OPENSSL_VERSION =
Ron Ramsay wrote:
Thanks for the extensive reply.
A part of your answer is reproduced below.
I don't think handling the depth internally (which is a good thing)
completely removes the need for a callback.
I agree, sometimes you need to handle "special" situations when verifying
in crypto/asn1 , many "unsigned char **pp",
like in crypto/asn1/asn1_lib.c ,define
void ASN1_put_object(unsigned char **pp, int constructed,
int length, int tag,int xclass)
why not just "unsigned char *pp" ?
__
OpenSSL Project
And I'm talking about a versioning system than handles that so long as
you remember that we don't support code based on development versions.
Of course that is reasonable. But then it would be nice if bugs in the
release versions were fixed faster. For example, version 0.9.2 has been
distributed
"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
Bodo Moeller wrote:
"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:
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"
gang cao wrote:
in crypto/asn1 , many "unsigned char **pp",
like in crypto/asn1/asn1_lib.c ,define
void ASN1_put_object(unsigned char **pp, int constructed,
int length, int tag,int xclass)
why not just "unsigned char *pp" ?
After reading/writing an ASN1 structure you almost always
in crypto/asn1 , many "unsigned char **pp",
Pointer to array of pointers to unsigned char
Sigh. Wrong. It's the address of a character pointer.
As Dr. Henson pointed out, the ASN1 routines typically
take a buffer pointer, parse some bytes, and update
the pointer. Hence the indirection. (In
In article [EMAIL PROTECTED] you wrote:
"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
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
(I've added a new entry
solaris-usparc-oldgcc for this which is the same as
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.
I'm currently using openssl 0.9.2b, and would like the ability to
enable/disable session ID caching. Is there a command or particular source
file I need to deal with in order to make this happen.
Thanks,
Vince
__
OpenSSL
16 matches
Mail list logo
