Moonraker wrote: ↑2020-09-25, 17:25
yes but how can you confirm the signing authority can be trusted also.?
Trust is a strange animal.
You may want to read up on certificate issuance, trust chains and trusted root certificates.
And contrary to what RealityRipple said the certificate isn't self-signed (that would be bad for an insurance provider!) but rather they have an incomplete certificate chain in their server configuration, missing one or more intermediate certificates.
To fix this they need to include the following two certificates in their server configuration:
KPN PKIoverheid Server CA 2020
Fingerprint SHA256: 592e1a2f0a34284b0e26fcb4fed22af859848eee8822adb61b42dab47a2ffdc2
Pin SHA256: Yao+RgzIlYNhXc65ch9IpKzSRFUSiL01Et8c6sN4XLU=
RSA 4096 bits (e 65537) / SHA256withRSA
Staat der Nederlanden Domein Server CA 2020
Fingerprint SHA256: 0da914fb7125f6e644eb7aa261de9eb809dc7f925b6b2a7d8a7edd8736398b5b
Pin SHA256: N9+YluTCUa/HTXc60QxjUReBLpRniAkIK2N84DhgmW4=
RSA 4096 bits (e 65537) / SHA256withRSA
While they are there they should also generate their own ECDH parameters since they are currently using public ones that makes them at risk of broken security if the public configuration key gets cracked.
"Son, in life you do not fight battles because you expect to win, you fight them merely because they need to be fought." --
Snagglepuss
