diff options
| author | Jakub Wilk <jwilk@jwilk.net> | 2018-04-17 21:17:57 +0200 |
|---|---|---|
| committer | Jay Satiro <raysatiro@yahoo.com> | 2018-04-17 15:32:51 -0400 |
| commit | 24e835587714289214002506aa0e2d59313f95c0 (patch) | |
| tree | f0370364e2b150a36a6e27d277e5277f527ba3b7 /docs/libcurl/libcurl-security.3 | |
| parent | ba48863e52ab042a6cf754e254dfb5062a45b090 (diff) | |
| download | curl-24e835587714289214002506aa0e2d59313f95c0.tar.gz | |
docs: fix typos
Closes https://github.com/curl/curl/pull/2503
Diffstat (limited to 'docs/libcurl/libcurl-security.3')
| -rw-r--r-- | docs/libcurl/libcurl-security.3 | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/libcurl/libcurl-security.3 b/docs/libcurl/libcurl-security.3 index 377301ee0..25ae400fe 100644 --- a/docs/libcurl/libcurl-security.3 +++ b/docs/libcurl/libcurl-security.3 @@ -75,7 +75,7 @@ doesn't let snoopers see your password: Digest, CRAM-MD5, Kerberos, SPNEGO or NTLM authentication. Or even better: use authenticated protocols that protect the entire connection and everything sent over it. .SH "Un-authenticated Connections" -Protocols that don't have any form of cryptographic authentication can not +Protocols that don't have any form of cryptographic authentication cannot with any certainty know that they communicate with the right remote server. If your application is using a fixed scheme or fixed host name, it is not safe |