Re: Compilation error on OpenStep 4.0
On Sat, Mar 18, 2000 at 06:42:21PM -0700, Francisco A Tomei Torres wrote: grep clock time.h typedef unsigned long int clock_t; clock_t clock(void); clock_t clock(); And can you locate CLOCKS_PER_SEC anywhere in some header file? Also, what does the clock() manual page say about what the return value means? __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: Pseudo Random Number Generator
On Fri, Mar 24, 2000 at 10:30:36PM -0800, David Ahrens wrote: [... BSAFE? ...] Bodo Moeller: David Ahrens: Does anyone know if the pseudo random number generator in openssl is FIPS-140 compliant? It doesn't do power-up self tests, so it can't be. If you happen to be a federal agency, I recommend you stay away from it. [...] I don't what components of BSAFE Crypto-C are FIPS 140-1 certified. They certainly have a certified triple-DES implementation (if you look at the Security-Navigator in Netscape you'll see that you DES-based ciphers appear in two variants, one of which mentions FIPS 140-1 and one of which does not), but they don't reveal much more. The certificate is at URL: http://rsasecurity.com/products/images/fips140-1_cert.gif: It is valid "[f]or services provided by the FIPS-approved algorithms listed on the reverse, and Triple DES". Of course they did not bother to scan the reverse :-) I'd be surprised if these certified algorithms include more than DES, SHA[-1], and DSS. __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: Compilation error on OpenStep 4.0
Hi, Francisco A. Tomei Torres [EMAIL PROTECTED]: cc -I../include -O -Wall -c ssltest.c -o ssltest.o ssltest.c: In function `main': ssltest.c:504: `CLOCKS_PER_SEC' undeclared (first use this function) Weird, this should be defined in time.h on every standard C system (it's not a POSIX special or something). Please grep through the standard header files to see if you can find this symbol anywhere. Also please read the manual page for the C function clock() and look for hints; it should say something like this: RETURN VALUE The value returned is the CPU time used so far as a clock_t; to get the number of seconds used, divide by CLOCKS_PER_SEC. In any case, please tell us if you've found something or not. NEXTSTEP/OPENSTEP has no define for CLOCKS_PER_SEC. There is a CLK_TCK define in "times.h": #ifdef _NEXT_SOURCE #import stddef.h #define CLK_TCK 64 #endif /* _NEXT_SOURCE */ and this is from the apache source code: #ifdef NEXT #if (NX_CURRENT_COMPILER_RELEASE == 410) #ifdef m68k #define HZ 64 #else #define HZ 100 #endif #else #include machine/param.h #endif #endif /* NEXT */ Maybe this helps? Bye, Juergen __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: Compilation error on OpenStep 4.0
Hi, > On Sat, Mar 18, 2000 at 06:42:21PM -0700, Francisco A Tomei Torres wrote: > > > grep clock time.h > > typedef unsigned long int clock_t; > > clock_t clock(void); > > clock_t clock(); > > And can you locate CLOCKS_PER_SEC anywhere in some header file? > Also, what does the clock() manual page say about what the return > value means? The is no manual page for the function clock() and there is no CLOCKS_PER_SEC define (NEXTSTEP/OPENSTEP). Bye, Juergen __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
