Microsoft Crypto. API - Wikipedia, the free encyclopedia. The Cryptographic Application Programming Interface (also known variously as Crypto. API, Microsoft Cryptography API, MS- CAPI or simply CAPI) is an application programming interface included with Microsoft Windowsoperating systems that provides services to enable developers to secure Windows- based applications using cryptography. It is a set of dynamically linked libraries that provides an abstraction layer which isolates programmers from the code used to encrypt the data. The Crypto API was first introduced in Windows NT 4.
Crypto. API supports both public- key and symmetric key cryptography, though persistent symmetric keys are not supported. It includes functionality for encrypting and decrypting data and for authentication using digital certificates. It also includes a cryptographically secure pseudorandom number generator function Crypt.
Gen. Random. Crypto. API works with a number of CSPs (Cryptographic Service Providers) installed on the machine. CSPs are the modules that do the actual work of encoding and decoding data by performing the cryptographic functions. Vendors of HSMs may supply a CSP which works with their hardware. Cryptography API: Next Generation[edit]Windows Vista features an update to the Crypto API known as Cryptography API: Next Generation (CNG). It has better API factoring to allow the same functions to work using a wide range of cryptographic algorithms, and the inclusion of a number of newer algorithms that are part of the National Security Agency (NSA) Suite B.[2] It is also flexible, featuring support for plugging in custom cryptographic APIs into the CNG runtime.
- Microsoft to drop Azure RemoteApp in favor of Citrix virtualization technologies. Microsoft is dropping its Azure RemoteApp technology over the course of the next.
- Products and open source. Microsoft’s cutting-edge research is changing the landscape of technology directly and behind the scenes. Researchers are embedded in the.
- Smart Card an SmartCard Reader Access for.NET Developers. The CardWerk SmartCard API is a product family that provides easy smart card access for developers.
However, CNG Key Storage Providers still do not support symmetric keys.[3] CNG works in both user and kernel mode, and also supports all of the algorithms from the Crypto. API. The Microsoft provider that implements CNG is housed in Bcrypt. CNG also supports elliptic curve cryptography which, because it uses shorter keys for the same expected level of security, is more efficient than RSA.[4] The CNG API integrates with the smart card subsystem by including a Base Smart Card Cryptographic Service Provider (Base CSP) module which encapsulates the smart card API. Smart card manufacturers just have to make their devices compatible with this, rather than provide a from- scratch solution. CNG also adds support for Dual_EC_DRBG,[5] a pseudorandom number generator defined in NIST SP 8. A that could expose the user to eavesdropping by the National Security Agency since it contains a kleptographic backdoor, unless the developer remembers to generate new base points with a different cryptographically secure pseudorandom number generator or a true random number generator and then publish the generated seed in order to remove the NSA backdoor.
It is also very slow.[6] It is only used when called for explicitly. CNG also replaces the default PRNG with CTR_DRBG using AES as the block cipher, because the earlier RNG which is defined in the now superseded FIPS 1. DES or SHA- 1, both which have been broken.[7] CTR_DRBG is one of the two algorithms in NIST SP 8. Schneier, the other being Hash_DRBG.[6]See also[edit]References[edit]^Poking Around Under the Hood: A Programmer's View of Windows NT 4. Suite B^Key Storage and Retrieval, Microsoft^The Case for Elliptic Curve Cryptography, NSA^Schneier, Bruce (December 1. Dual_EC_DRBG Added to Windows Vista". Schneier on Security.
Retrieved January 1. Schneier, Bruce (November 1. The Strange Story of Dual_EC_DRBG". Schneier on Security. Retrieved January 1. FIPS PUB 1. 86- 2"(PDF).
Smart Card minidrivers are implemented according to the Windows Smart Card Minidriver Specification. The following specifications prescribe the version and related.
Describes a framework to use the PCSC Smart Card API with.NET.; Author: orouit; Updated:; Section: Smart Client; Chapter: Desktop Development; Updated.
Federal Information Processing Standards. National Institute of Standards and Technology. January 2. 7, 2. 00. Retrieved January 1. External links[edit].
Smart Card software development . NET framework SDKSmart Card API and . NET Framework for C# and VB. NET Developers. Smart Card an Smart. Card Reader Access for .
NET Developers. The Card. Werk Smart. Card API is a product family that provides. Microsoft. . NET environment. The Smart. Card API class libraries support all. NET programming languages such as Visual Basic. NET, Visual C#. and many others.
It can even be used from code hosted inside Microsoft. Internet Explorer. The full version of our Smart.
Card API development kits may be. A development kit license. Your Advantages. No need to mess around with P/Invoke and winscard. Save time and money by using tested. NET classes. Purchase of a commercial license grants Royalty Free redistribution. Protect your investment: The complete C# source code is available for.
Get started quickly: All editions include sample applications and. Risk Free: evaluation versions are fully functional.
Full Service: We offer maintenance contracts, on site training and. CLASS, DESFire EV1, Mifare, Java. Card, MULTOS to name a few.
Editions to match your needs. Card. Werk Smart. Card API is available in three editions in order to provide the best possible solution for your development needs: Smart. Card API (Professional)The Professional edition implements the powerful Smart. Card API Framework that supports accessing smart card readers through the Windows native.
PC/SC Workgroup API (Win. SCard) and the German CT- API. In addition access to memory cards is supported through proprietary storage card API and CT- API. We currently support SCM Microsystems Inc.' MCARD API adapter class. Contact storage cards on OMNIKEY readers are supported via OMNIKEY SCARDSYN wrapper class.
CLASS card support is available upon request. The Professional version is the ideal edition to get started with US Government PIV and CAC cards via both contact (ISO 7. ISO 1. 44. 43, ISO 1. PC/SC- based industry standards compliant readers. Smart. Card API (Express)The Express edition provides low overhead access to asynchronous smart cards through the native Microsoft Windows Win.
SCard DLL (defined by PC/SC Workgroup API). It is the most cost effective solution if you do not require support for CT- API, memory cards and you don't need the advanced, event- driven card tracking capabilities of Smart. Card API Professional edition. Smart. Card API (Windows CE)The Windows CE edition extends the .
NET Compact Framework with smart card access through the Win. SCard module of Windows CE based devices, such as Windows Mobile 5. Pocket PC devices. Check it out. Download the free, fully functional evaluation version now!
Copyright 2. 00. 4- 2. Card. Werk Technologies, All rights reserved.
Imrint, Legal Disclaimer. Last modified August 2, 2.