master-server/deps/curl/docs/cmdline-opts/insecure.md

42 lines
1.4 KiB
Markdown
Raw Normal View History

2024-05-15 15:20:32 -04:00
---
2023-12-11 20:30:44 -05:00
c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
SPDX-License-Identifier: curl
Long: insecure
Short: k
Help: Allow insecure server connections
Protocols: TLS SFTP SCP
Category: tls sftp scp
Added: 7.10
Multi: boolean
2024-05-15 15:20:32 -04:00
See-also:
- proxy-insecure
- cacert
- capath
Example:
- --insecure $URL
2023-12-11 20:30:44 -05:00
---
2024-05-15 15:20:32 -04:00
# `--insecure`
2023-12-11 20:30:44 -05:00
By default, every secure connection curl makes is verified to be secure before
the transfer takes place. This option makes curl skip the verification step
and proceed without checking.
When this option is not used for protocols using TLS, curl verifies the
server's TLS certificate before it continues: that the certificate contains
2024-05-15 15:20:32 -04:00
the right name which matches the hostname used in the URL and that the
certificate has been signed by a CA certificate present in the cert store. See
this online resource for further details:
**https://curl.se/docs/sslcerts.html**
2023-12-11 20:30:44 -05:00
For SFTP and SCP, this option makes curl skip the *known_hosts* verification.
*known_hosts* is a file normally stored in the user's home directory in the
2024-05-15 15:20:32 -04:00
".ssh" subdirectory, which contains hostnames and their public keys.
2023-12-11 20:30:44 -05:00
**WARNING**: using this option makes the transfer insecure.
When curl uses secure protocols it trusts responses and allows for example
HSTS and Alt-Svc information to be stored and used subsequently. Using
--insecure can make curl trust and use such information from malicious
servers.