Lines Matching refs:DN

64  *     -- Start of the issuer DN: the secondary hash engine is started,
65  *     to process the encoded issuer DN.
67  *     -- End of the issuer DN: the secondary hash engine is stopped. The
71  *     -- Start of the subject DN: the secondary hash engine is started,
72  *     to process the encoded subject DN.
77  *     -- End of the subject DN: the secondary hash engine is stopped. The
84  *        -- Otherwise, the hashed subject DN is compared with the saved
89  *     contains the hash of the issuer DN for the current certificate,
90  *     and current_dn_hash[] contains the hash of the subject DN for the
99  *        DN are also compared with the "direct trust" keys; if the key
100  *        and DN are matched, then validation ends with a success.
142  *     -- Certificate end: the hashed issuer DN (saved_dn_hash[]) is
300  * Hash a DN (from a trust anchor) into the provided buffer. This uses the
301  * DN hash implementation and context structure from the X.509 engine
499 \ Start DN hash computation.
505 \ Terminate DN hash computation and write the DN hash into the
512 \ Get the length of hash values obtained with the DN hasher.
529 \ Read a DN, hashing it into current_dn_hash. The DN contents are not
531 : read-DN ( lim -- lim )
634 \ Read a DN for the EE. The normalized DN hash is computed and stored in the
640 : read-DN-EE ( lim -- lim bool )
645 	\ Activate DN hashing.
648 	\ Parse the DN structure: it is a SEQUENCE of SET of
695 	\ Compute DN hash and deactivate DN hashing.
764 \ starting wildcard, and only against a complete DN name component.
1205 	read-DN
1218 		read-DN-EE { eename }
1220 		\ For a non-EE certificate, the hashed subject DN must match
1221 		\ the saved hashed issuer DN from the previous certificate.
1222 		read-DN
1226 	\ Move the hashed issuer DN for this certificate into the