summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorcorvid <devnull@localhost>2016-07-06 14:06:52 +0000
committercorvid <devnull@localhost>2016-07-06 14:06:52 +0000
commitc11eebf3011ca060f32e3c7f96f3100850da356d (patch)
treed176a84b1545186248ccaa7a380d7c0f7897cd71
parent61e86fe3dfaf4fa96cb5207e69bde51c7869f96e (diff)
MSG clarification
You can trust an intermediate certificate in a chain, so let's be careful with words here. It would of course be better to tell the user which certificate was trusted in that case, but my understanding is that I would have to go through each certificate in the chain and try to match it against all of the trusted certificates, like mbed tls's verification code does in the first place. This would involve a lot of digging around in mbed tls's structures and using resources...
-rw-r--r--src/IO/tls.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/IO/tls.c b/src/IO/tls.c
index 91b69be0..5785d64b 100644
--- a/src/IO/tls.c
+++ b/src/IO/tls.c
@@ -1110,7 +1110,7 @@ static void Tls_cert_authorities_print_summary()
int i, j;
if (ca_len)
- dStr_append(ds, "TLS: Trusted during this session:\n");
+ dStr_append(ds, "TLS: Certificate chain roots during this session:\n");
for (i = 0; i < ca_len; i++) {
CertAuth_t *ca = (CertAuth_t *)dList_nth_data(cert_authorities, i);