F-Secure Corp. not reacting to wrecking of "corp-reg" HTTPS address by latest Microsoft IE hotfix?
Dear F-Secure Corp,
Some customers are reporting that F-Secure Policy Manager 12 is no longer able to connect and activate (do customer validity check) at the website address "https://corp-reg.f-secure.com:443/"
If checked manually, the website loads OK in Firefox 53.0.2 or Chrome 58 browsers and displays the usual one line human readable message: "F-Secure corporate registration server. Unauthorized access is monitored and strictly forbidden." However trying the visit same site in IE 11 results in an error 403 forbidden / refused connection. (I don't know if the visit is forbidden at the client or server side.)
I think proxy use must not be a problem, because Google Chrome also applies the Windows user's proxy settings, the same like IE.
Therefore I theorize Microsoft Corp. must have broken some compatibility with their latest IE hotfix published as part of the May 9th "Patch Tuesday"? (Possibly something related to the depreciation of SHA-1 ciphers?)
Maybe in consequence, FSPM, which uses IE infrastructure, also became unable to connect and then verify licence, thus blocking PM Console's login, leaving users high and dry?
When successfully connecting in FF 53 or Chrome 58, the networking properties are displayed as such: Protocol: TLS 1.2, Key exchange: ECDHE_RSA with P-256, Cipher: AES_256_GCM / SHA-384
Please give me a very urgent response regarding this issue?
Thanks in advance, Yours Sincerely:
Tamas Feher, Hungary.