Security

IIS Crypto Updated

We just published a minor update of IIS Crypto. If you have been experiencing a crash while running from a network share, this resolves the issue.

16 thoughts on “IIS Crypto Updated”

  1. I know this question has been asked before but it hasn't been answered.

    I am running a website Asp.Net + IIS 8.5.

    I have the enable client side protocol set – What does it do, need to keep it set? I have no control over clients (browser)? Do I need to keep it ticked?

    Like

    5. IIS Crypto reaches out to mail.nartac.com during SSL removal with TCP connect
      It preforms TCP TCPCopy, TCP Send TCP Receive commands. Why is it reaching out to your servers across the net?

      Like

    6. Hi,

      It reaches out to update.nartac.com which is the same IP address as mail.nartac.com. It does a check for updates. That is the only external server it hits.

      – Jeff

      Like

    7. Thank you kindly for designing and providing this tool! I don't think it could have been made to work any easier!

      Like

    8. In July 2017, Microsoft released update KB4019276 to add TLS1.1 and TLS1.2 to Server 2008 (Windows 6.00) Service Pack, will there be an updated version of IISCrypto supporting this, or will everybody have to revert back to manual configuration again?

      Like

    9. Bug Report

      Version: Version 2.0 Build 11, both GUI and CLI
      Windows: Server 2016 Datacenter, Azure VM, fully patched (June cumulative).

      Crash on launch of GUI, or crash when trying to apply template via CLI.

      Errors from Event viewer and CLI
      KERNELBASE.DLL and System.InvalidCastException

      Like

    11. After Installing the ICC Server Hardening modules application was running fine, But all of the sudden server (windows 2008
      and windows 2016 servers )got rebooted , TLS 1.2 registry values are not reflected .Application is also not working.

      Like

    12. Is it planned to release a new version of IISCrypto anytime soon which reflects the new requirements of PCI 3.2 and also handles the new cipher suites?
      There were quite some changes since 2016…

      Like

    13. I cannot get IIS Crypto to run on our Azure IaaS VMs. The latest version presents the agreement, I click next and it fails to run. The Application event logs are stating "System.InvalidCastException" error in .NET. Does anyone have any suggestions?

      Like

Comments are closed.