Looks like only app_verify_callback in ssl_st is missing a prototype.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List
[[EMAIL PROTECTED] - Sat Aug 17 15:51:29 2002]:
...
You should take a closer look at 0.9.7 (currently in beta), where a
some of the stricter type handling has already been applied.
We will probably not apply your change to the 0.9.6 line of
development, because it's a rather big change,
Lutz Jaenicke via RT wrote:
We will probably not apply your change to the 0.9.6 line of
development, because it's a rather big change, and we try to avoid
that within the same line of development (for now, 0.9.x is a line of
development, so 0.9.7 is a different one, as is 0.9.8 (in development
Richard Levitte - VMS Whacker writes:
Have you looked at lhash.h, and the DECLARE_LHASH*/IMPLEMENT_LHASH*
macros? That's how we have started to solve the type problems. Yes,
the generated functions contain some internal casting, but in such a
way that they don't affect the code that use
Rainer Orth wrote:
With the introduction of public key cryptography into the Network Time
Protocol (NTP v4, cf. http://www.ntp.org/), the current version of NTP
became a heavy user of OpenSSL.
NTP developers strive to keep the sources warning-free with gcc (using
-Wall -Wcast-qual
In message [EMAIL PROTECTED] on Mon, 19 Aug
2002 15:08:03 +0200 (MEST), Rainer Orth [EMAIL PROTECTED] said:
ro Richard Levitte - VMS Whacker writes:
ro
ro You should take a closer look at 0.9.7 (currently in beta), where a
ro some of the stricter type handling has already been applied.
ro
Ulf Möller writes:
Thats is a very useful patch, however there will be no more releases on the
0.9.6 branch unless major problems are found. Probably much of the patch
also applies to the main development branch, but it can't be applied
directly.
Do you think this is appropriate for the
Ben Laurie [EMAIL PROTECTED] writes:
[Please keep me on the Cc:, since I'm not subscribed to openssl-dev. Thanks.]
This patch removes typesafety by using casts with gay abandon. Why is
this necessary? More to the point, IMO it should not be necessary. I'm
not keen on introducing a patch
Richard Levitte - VMS Whacker writes:
You should take a closer look at 0.9.7 (currently in beta), where a
some of the stricter type handling has already been applied.
I think I had a quick look at the CVS mainline, and the problems were still
present there. Unless there are patches in the
With the introduction of public key cryptography into the Network Time
Protocol (NTP v4, cf. http://www.ntp.org/), the current version of NTP
became a heavy user of OpenSSL.
NTP developers strive to keep the sources warning-free with gcc (using
-Wall -Wcast-qual -Wmissing-prototypes
In message [EMAIL PROTECTED] on Fri, 16 Aug
2002 23:32:19 +0200 (MEST), Rainer Orth [EMAIL PROTECTED] said:
ro With the introduction of public key cryptography into the Network Time
ro Protocol (NTP v4, cf. http://www.ntp.org/), the current version of NTP
ro became a heavy user of OpenSSL.
ro
With the introduction of public key cryptography into the Network Time
Protocol (NTP v4, cf. http://www.ntp.org/), the current version of NTP
became a heavy user of OpenSSL.
NTP developers strive to keep the sources warning-free with gcc (using
-Wall -Wcast-qual -Wmissing-prototypes
In message [EMAIL PROTECTED] on Fri, 16 Aug
2002 23:32:19 +0200 (MEST), Rainer Orth [EMAIL PROTECTED] said:
ro With the introduction of public key cryptography into the Network Time
ro Protocol (NTP v4, cf. http://www.ntp.org/), the current version of NTP
ro became a heavy user of OpenSSL.
ro
13 matches
Mail list logo
