The docs call out that this field is the algorithm used to sign the certificate. However, the example only had the hash portion of the signature algorithm. This change updates the example to be accurate based on a value written by HAProxy, which is based on an OID for signature algorithms. I based example on a real TLV written by HAProxy on my machine with all SSL TLVs enabled in config. --- doc/proxy-protocol.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/proxy-protocol.txt b/doc/proxy-protocol.txt index fac033176..75a7e1f74 100644 --- a/doc/proxy-protocol.txt +++ b/doc/proxy-protocol.txt @@ -654,7 +654,7 @@ of the used cipher, for example "ECDHE-RSA-AES128-GCM-SHA256". The second level TLV PP2_SUBTYPE_SSL_SIG_ALG provides the US-ASCII string name of the algorithm used to sign the certificate presented by the frontend when the incoming connection was made over an SSL/TLS transport layer, for example -"SHA256". +"RSA-SHA256". The second level TLV PP2_SUBTYPE_SSL_KEY_ALG provides the US-ASCII string name of the algorithm used to generate the key of the certificate presented by the -- 2.39.5 (Apple Git-154)
