What is happening here? Eset is blocking the official site of the Dutch Data Protection Authority The site is https://autoriteitpersoonsgegevens.nl/ Wikipedia NL https://nl.wikipedia.org/wiki/Autoriteit_Persoonsgegevens Wikipedia EN https://en.wikipedia.org/wiki/Dutch_Data_Protection_Authority SSL Checker: https://www.sslshopper.com/ssl-checker.html#hostname=https://autoriteitpersoonsgegevens.nl/ What is this kind of nonsense?
https://www.ssllabs.com/ssltest/analyze.html?d=autoriteitpersoonsgegevens.nl autoriteitpersoonsgegevens.nl Fingerprint SHA256: b73bc7a6e1b5cdebf1e857340b35954e99bc2fcbf697ab1482f136422e83cd65 Pin SHA256: mF/9bd715GdCFCNTtTc8TeU5+qlTiQfrz77okH6lCkM= RSA 2048 bits (e 65537) / SHA256withRSA REVOKED
The issue is explained (alas only in Dutch) here on this official site: Intrekking PKIoverheid certificaten https://www.logius.nl/actueel/blog-pkioverheid-certificaat-vervangingsplan They know about it. It will be fixed. According to that site it will be fixed on 31 January 2021, as far as I understand it. Well, let's wait and see... ESET is not to blame, in no way!!
And I was wrong there too. There is a .pdf file in English at the NCSC-NL site: https://english.ncsc.nl/binaries/ncsc-en/documents/factsheets/2020/12/22/factsheet-pkioverheid-is-changing-coordinate-the-necessary-changes-in-your-ict-processes/Factsheet+PKIoverheid+is+changing+v1.0.pdf
To end this story: I tried it again and nomore problems. So, it must have been fixed on their end. I would like to thank @Marcos again for pointing me in the right direction! After his post (and some other contacts) I suddenly did realize that the problem was far more spread on official Dutch sites and that I did read about it before (but had forgotten about). Let's hope that the issue on other official Dutch sites is fixed too (or will be fixed by the end of January). Once again: this was in no way caused by ESET !! End of story
