Important: |
---|
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
Cryptography Services for Windows Embedded CE-based devices provide services that enable application developers to add security to applications using cryptography. It includes functionality for encoding to and decoding from ASN.1, for hashing, encrypting, and decrypting data, for using digital certificate, and for managing certificates.
Windows Embedded CE 6.0 Cryptography Services with High
Encryption Provider is FIPS 140-2, level 1 certified. For more
information about FIPS certification for Windows Embedded CE 6.0,
see this
OS Design Information
The following table shows operating system design information for Cryptography.
Element | Information |
---|---|
Dependencies |
Smart Card CSP requires the Smart Card Resource Manager and CryptoAPI 1.0. |
Hardware considerations |
None. |
Modules and Components
The following table shows the components and modules that implement Cryptography Services.
Item | Module | Component |
---|---|---|
Cryptography Services (CryptoAPI 1.0) with High Encryption Provider |
coredll, rsaenh |
coredll module: cryptapi |
Low Encryption Provider (Microsoft Base Cryptographic Service Provider) |
rsabase |
None |
Cryptography Services Implementation Considerations
The following table shows the Sysgen variables that enable Cryptography Services.
Sysgen variable | Description |
---|---|
SYSGEN_CRYPTO |
Cryptography Services (CryptoAPI 1.0) provides a set of cryptographic services for hashing, encrypting, and decrypting data. |
SYSGEN_CRYPTO_DSSDH |
Diffie-Hellman/DSS provider supports hashing, generating, exchanging, and exporting Diffie-Hellman keys. |
See Also
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.