Try the latest 0.9.8 snapshot: a whole load of such warnings have been fixed since the 0.9.8a release.
For reference, http://marc.theaimsgroup.com/?t=113195805500002&r=1&w=2 discusses this. Note that is also mentions alternative workaround for "possible loss of data" when assigning value returned by time(). It mentions that I'd like to give it some "further consideration." For reference my concern is that computers and communication lines are so fast nowadays that using 1 second granularity timer in some of those places might be inappropriate and that we might consider switching to higher resolution timer... A.
______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [EMAIL PROTECTED]
