<html xmlns="http://www.w3.org/1999/xhtml"><head></head><body><figure class="quote"><figcaption><p><anchor-end xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:anchor="1" xmlns:a0="urn:x-suika-fam-cx:markup:suikawiki:0:9:">[1]</anchor-end> <cite xml:lang="en">RFC 6125 - Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)</cite>
(<time>2015-03-13 22:27:53 +09:00</time> 版)
<anchor-external xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:resScheme="URI" xmlns:a0="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:resParameter="https://tools.ietf.org/html/rfc6125#section-1.8">https://tools.ietf.org/html/rfc6125#section-1.8</anchor-external></p></figcaption><blockquote><p>pinning:  The act of establishing a cached name association between</p><p>the application service's certificate and one of the client's</p><p>reference identifiers, despite the fact that none of the presented</p><p>identifiers matches the given reference identifier.  Pinning is</p><p>accomplished by allowing a human user to positively accept the</p><p>mismatch during an attempt to communicate with the application</p><p>service.  Once a cached name association is established, the</p><p>certificate is said to be pinned to the reference identifier and</p><p>in future communication attempts the client simply verifies that</p><p>the service's presented certificate matches the pinned</p><p>certificate, as described under Section 6.6.2.  (A similar</p><p>definition of &quot;pinning&quot; is provided in <strong>[</strong>WSC-UI<strong>]</strong>.)</p></blockquote></figure></body></html>