Closed mac1024it closed 7 months ago
Sorry, but this bug report is not helpful at all. Right now I have no choice but to close this ticket as "works for me".
Please provide a concrete example or steps to reproduce your issue.
Ok, after two weeks have passed, I don't expect to receive any response anymore. Therefore closing this issue... There is a reason for the bug report template and there is a reason that the bug template contains the suggestion to check back after a few days.
SHA-256 fingerprint of the current Google certificate in KSE and OpenSSL:
$ openssl s_client -connect www.google.com:443 < /dev/null 2>/dev/null | openssl x509 -fingerprint -sha256 -noout -in /dev/stdin
sha256 Fingerprint=02:4B:48:FD:66:0C:18:8E:2F:DB:F9:D3:F0:29:DC:5C:13:62:D0:F0:0C:67:93:BF:71:47:E9:F2:33:54:C3:01
Describe the bug Examining a certificate KSE fingerprint function gives SHA-1 and SHA-256 wrong hash values
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Environment