Lines Matching full:applications

27 Many applications are used in closed networks where users and servers can
30 some risks in the ways in which applications commonly use libcurl and
32 classes of attacks that robust applications should consider. The Common
57 For applications that enable .netrc use, a user who manage to set the right
107 enabled by default. Applications may opt to restrict that set further.
133 Applications can mitigate against this by disabling
159 10.1.2.3. Applications can mitigate against this by setting a
167 and display the result. Applications can mitigate against this with the
173 behind a firewall. Applications can mitigate against this by using the
212 overwritten. Applications must not allow any unsanitized URL to be passed in
214 uploads. Instead, the applications should consider handling redirects itself,
220 information to be sent to an unknown second server. Applications can mitigate
239 **http://mail.example.com/delete-stuff.cgi?delete=all** Applications can
249 Applications must not allow unsanitized SCP: URLs to be passed in for
264 applications to disable it, to establish a connection to another host over the
269 order to protect applications for inadvertent probes of for example internal
290 Applications may find it tempting to let users set the URL that it can work
386 sufficient to guard against this. Instead, applications should monitor the
417 enabled by applications that fail to properly validate server TLS/SSL
440 # setuid applications using libcurl
442 libcurl-using applications that set the 'setuid' bit to run with elevated or
469 When applications pass usernames, passwords or other sensitive data to