Home
|
FAQ
|
Feedback
|
Licence
|
Updates
|
Mirrors
|
Keys
|
Links
|
Team
Download:
Stable
·
Pre-release
·
Snapshot
|
Docs
|
Privacy
|
Changes
|
Wishlist
We did once have some sort of optional support for the Microsoft Crypto API, but it rotted, and didn't support all the algorithms we needed (eg Blowfish), so was eventually removed.
Quoth Simon:
My other concern about CryptoAPI is the whole idea of handing a MS-controlled function a pointer and saying `here, take a look at my plaintext'. Not that I think MS is likely to be bugging that function (as it were) at the moment, but there's no point in making it easy for someone to install a modified DLL and trojan all cryptography done in the system.
On the other hand, it might be good to be able to make use of the thermal noise-based random number generators now appearing in some commodity chipsets such as the Intel 810 FWH. These might be exposed through the Crypto API.
May also be relevant to smartcard-auth.
Any support would have to be optional (controlled by configuration option? Test for presence of API?). Probably an application for the MDPI.
SGT, 2024-11-17: classifying this wish as dormant. The main motivation was to enable the same PuTTY executable to support SSH where cryptography was legal, and fall back to being basically PuTTYtel where it wasn't. But cryptograph is more widely legal now (France in particular stopped being awkward), and also, now that the unencrypted network protocols are all very historical, it's not much use without encryption any more.