In relation to FIPS compliance, what is the situation of SQLCE 3.5 while running on Windows Mobile 6.0?
I have read many different reports about this and need a definitive answer, which comes from a reliable source (please provide link)
I read this "SQL Server Compact 3.5 has encryption mode FIPS compliant if FIPS mode is enabled at the OS level."
Is this true? If so, then how is it enabled at the OS level?
This means that you support AES 128 in the OS image and if it is there, then SQL Compact engines will use it. In Windows CE, if you are creating OS, which part of the crypto can you decide, and I believe AES128 is a part of the standard crypto offering (I can not verify because I do not have a PC.
For Windows Mobile, you can not do anything to turn it on or off - it is either or it is still available on the platform builder for me. T. Early versions (e.g. old Kocket PC and Pocket PS 2003 IIRC) were sent only as OEMs in the form of 56-bit encryption. Based on Microsoft's published information, it looks like WinMo 5.0 and later all the codes are compatible. < / P>
No comments:
Post a Comment