diff options
| author | corvid <devnull@localhost> | 2016-07-06 14:06:52 +0000 |
|---|---|---|
| committer | corvid <devnull@localhost> | 2016-07-06 14:06:52 +0000 |
| commit | c11eebf3011ca060f32e3c7f96f3100850da356d (patch) | |
| tree | d176a84b1545186248ccaa7a380d7c0f7897cd71 /src/IO/http.c | |
| parent | 61e86fe3dfaf4fa96cb5207e69bde51c7869f96e (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...
Diffstat (limited to 'src/IO/http.c')
0 files changed, 0 insertions, 0 deletions