> On 03/23/11 11:56 AM, Greaves, Ed (GE Healthcare) wrote: >> Windows CE 6.0 and 7.0 for ARM. > > 7 was released this month, right? I'd imagine there will be a > development effort spend on it when someone takes it on for their own > requirements. > > but I thought Windows-centric stuff generally used the Microsoft > certificate services, CAPI and so forth, and CryptoAPI as thats all > integrated into their .NET view of the World According to Microsoft ?
OK, let me request Windows CE 5.0 which is currently supported by OpenSSL. The OpenSSL FIPS module is listed as not supported under Windows CE in the FIPS user's guide. The reason I'm using OpenSSL is that I'm integrating with another library that supports it. I'd like my implementation to be portable to a range of platforms including Windows, Windows CE on ARM, and other non-Windows platforms yet to be determined. As there is no OpenSSL FIPS module on Windows CE, I will probably use the Windows CE API for SSL support as it is FIPS validated. I was hoping to avoid this because it is extra work and I'm not sure how well it will integrate with the library. -Ed ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
