IIS Crypto 4.0 has been released! New features include Windows Server 2025 support, HTTP/3 with QUIC, full logging for both the GUI and CLI versions, view current settings for the CLI, updated templates and a lot more under the hood. https://t.co/10Uq8M3j97
IIS Crypto 4.0 almost ready! New features include Windows Server 2025 support, HTTP/3 with QUIC, logging for GUI and CLI, view current settings for CLI, all templates updated and more.
@n176053 Hi, it looks like you are using Server 2012. They can be enabled, but they are not required for client connections. See our FAQ about it here: https://t.co/wTX4ms0s9e
IIS Crypto 3.2 has been released. This version includes a new checkbox for overriding the Enabled value for Protocols. See our blog post for more information. https://t.co/uHGkZdUMnA
We have been getting a lot of questions as to why IIS Crypto sets the Enabled registry key value to 0xffffffff instead of 1. Here is an explanation https://t.co/AqnfNSYZGU We have added a new feature to override the Enabled setting. It should be released in the next day or two.
IIS Crypto 3.1 has been released! This is a minor update that fixes a couple of issues before the next release which will have new features. Download it here https://t.co/Ng65KEKzJ0
@jwckauman Sorry for the long delay, notifications were not working for the last few weeks. A new version is coming to address bugs and update our code signing cert. New features will follow that version. Unfortunately TLS 1.3 is still not implemented by Microsoft.
@Winstanley_John Sorry for the really long delay, notifications were not working. 3DES is actually disabled in the cipher suites which is where it matters most. You generally don't want to disable it in the main screen as those are schannel settings which are used by other applications.