RFC 7030 and CSR recreation due to new session causing new tls-unique value
Michael Ross <[email protected]> Thu, 31 Jan 2019 16:51:51 -0500
| Newsgroups | gmane.comp.encryption.bouncy-castle.devel |
|---|---|
| Message-ID | <[email protected]> |
RFC 7030 section 3.2.1 at https://tools.ietf.org/html/rfc7030#section-3.2.1 states "Additionally, if the client has already generated a CSR that includes linking identity and POP information (Section 3.5), then the CSR will need to be recreated to incorporate the tls-unique from the new, redirected session." RFC 7030 section 4.2.3 at https://tools.ietf.org/html/rfc7030#section-4.2.3 states "If the client closes the TLS connections while waiting for the Retry-After time to expire, then the client initiates a new TLS connection and performs all applicable security checks. If the client has already generated a CSR that includes linking identity and POP information (Section 3.5), then the CSR will need to be recreated to incorporate the tls-unique from the new, redirected session." Where is the code that fulfills this requirement? I have not been able to locate it. I am sorry for asking such a stupid question. I am new here. Thank you. Very Respectfully, Michael Ross
smime.p7s
(application/pkcs7-signature, 4.5 KB) - not displayed