Searched refs:clear (Results 1 – 25 of 25) sorted by relevance
/curl/docs/cmdline-opts/ |
H A D | ftp-ssl-control.md | 5 Help: Require TLS for login, clear for transfer 18 Require SSL/TLS for the FTP login, clear for transfer. Allows secure
|
H A D | krb.md | 16 - --krb clear ftp://example.com/ 22 be one of 'clear', 'safe', 'confidential', or 'private'. Should you use a
|
H A D | digest.md | 22 the password over the wire in clear text. Use this in combination with the
|
H A D | proxy-user.md | 29 similar and never used in clear text in a command line.
|
H A D | user.md | 33 similar and never used in clear text in a command line.
|
/curl/docs/libcurl/opts/ |
H A D | CURLMOPT_PIPELINING_SITE_BL.md | 36 Pass a NULL pointer to clear the block list.
|
H A D | CURLMOPT_PIPELINING_SERVER_BL.md | 41 Pass a NULL pointer to clear the block list.
|
H A D | CURLOPT_FTP_SSL_CCC.md | 65 /* go back to clear-text FTP after authenticating */
|
H A D | CURLOPT_HSTS_CTRL.md | 35 the client to not contact it again over clear-text HTTP for a certain period
|
H A D | CURLOPT_KRBLEVEL.md | 31 of the following: &'clear', &'safe', &'confidential' or &'private'. If the
|
H A D | CURLINFO_OS_ERRNO.md | 38 transfer. Prior versions did not clear the saved errno, which means if a saved
|
H A D | CURLOPT_TCP_NODELAY.md | 31 cleared (1L = set, 0 = clear). The option is set by default. This has no
|
H A D | CURLOPT_HSTS.md | 37 without reading from or writing to any file. NULL also makes libcurl clear the
|
H A D | CURLOPT_HTTP_VERSION.md | 66 cannot be negotiated with the HTTPS server. For clear text HTTP servers,
|
H A D | CURLOPT_QUOTE.md | 37 curl_slist_append(3) to append strings (commands) to the list, and clear
|
H A D | CURLINFO_TLS_SSL_PTR.md | 117 This option has not been thoroughly tested with clear text protocols that can
|
/curl/docs/libcurl/ |
H A D | curl_multi_poll.md | 88 events such as the socket being clear to write without blocking. 117 myown.revents = 0; /* clear it */
|
H A D | curl_multi_wait.md | 81 write events such as the socket being clear to write without blocking.
|
H A D | libcurl-security.md | 52 clear text and is a real security risk. In some cases, your .netrc is also 54 based file system, so the clear text password flies through your network every 66 clear text (HTTP Basic authentication, FTP, TELNET etc). It is easy for anyone 225 and password being sent in clear text to an HTTP server. Instead, use 230 username and password being sent in clear text to an FTP server. Instead, use 478 needed, libcurl does not explicitly clear memory before freeing it, so
|
H A D | libcurl-tutorial.md | 426 method is called 'Basic', which is sending the name and password in clear-text 763 therefore necessary to clear it for *CURLFORM_FILECONTENT* emulation.
|
/curl/lib/ |
H A D | multi.c | 1589 static bool multi_ischanged(struct Curl_multi *multi, bool clear) argument 1592 if(clear) 1944 bool clear = FALSE; 1962 clear = TRUE; 1977 clear = TRUE; 1981 if(clear) {
|
/curl/docs/ |
H A D | KNOWN_BUGS | 51 6.7 Do not clear digest for single realm 339 6.7 Do not clear digest for single realm
|
H A D | TODO | 434 However: most secrets are passed to libcurl as clear text from the 736 using the simple authentication mechanism (as clear text). However, it should
|
H A D | FAQ | 889 The first part is to avoid having clear-text passwords in the command line
|
/curl/.github/workflows/ |
H A D | windows.yml | 623 VCPKG_BINARY_SOURCES: 'clear;x-gha,readwrite'
|
Completed in 177 milliseconds