Closed wrygiel closed 8 years ago
If I understood you correctly:
fingerprint
attribute to match the client's certificate, and allow it to access the resource, without validating the body of the <certificate>
attribute.Is this correct?
We are considering to host public key fingerprints only, so this becomes more important. I guess it won't hurt anyone if we switch to SHA-256, just in case. And it will make us look more secure once SHA-1 is finally broken. ;)
Sounds good to me :-)
Sent from my iPhone
On 12 Feb 2016, at 19:09, Wojciech Rygielski notifications@github.com wrote:
We are considering to host public key fingerprints only, so this becomes more important. I guess it won't hurt anyone if we switch to SHA-256, just in case. And it will make us look more secure once SHA-1 is finally broken. ;)
— Reply to this email directly or view it on GitHub.
Released in Discovery Manifest API v2.0.0.
In https://github.com/erasmus-without-paper/ewp-specs-api-echo/issues/2 @andydowling-ie wrote:
and, later on: