Linking Identity and POP Information (tls-unique) #2
Description
First of all, I want to say that I really like this EST client. Great job!
I want to check if the "Linking Identity and POP Information" as described it https://tools.ietf.org/html/rfc7030#section-3.5 is supported? I don’t see it listed in https://github.com/thales-e-security/estclient#analysis-of-rfc-requirements
3.5. Linking Identity and POP Information
Server policy will determine whether clients are required to use the
mechanism specified in this section. This specification provides a
method of linking identity and proof-of-possession by including
information specific to the current authenticated TLS session within
the signed certification request. The client can determine if the
server requires the linking of identity and POP by examining the CSR
Attributes Response (see Section 4.5.2). Regardless of the CSR
Attributes Response, clients SHOULD link identity and POP by
embedding tls-unique information in the certification request. If
tls-unique information is included by the client, the server MUST
verify it. The EST server MAY reject requests without tls-unique
information as indicated by server policy.