Lines Matching full:applications

26 Many applications are used in closed networks where users and servers can
29 some risks in the ways in which applications commonly use libcurl and
31 classes of attacks that robust applications should consider. The Common
56 For applications that enable .netrc use, a user who manage to set the right
106 enabled by default. Applications may opt to restrict that set further.
132 Applications can mitigate against this by disabling
158 10.1.2.3. Applications can mitigate against this by setting a
166 and display the result. Applications can mitigate against this with the
172 behind a firewall. Applications can mitigate against this by using the
211 overwritten. Applications must not allow any unsanitized URL to be passed in
213 uploads. Instead, the applications should consider handling redirects itself,
219 information to be sent to an unknown second server. Applications can mitigate
238 **http://mail.example.com/delete-stuff.cgi?delete=all** Applications can
248 Applications must not allow unsanitized SCP: URLs to be passed in for
263 applications to disable it, to establish a connection to another host over the
268 order to protect applications for inadvertent probes of for example internal
289 Applications may find it tempting to let users set the URL that it can work
385 sufficient to guard against this. Instead, applications should monitor the
416 enabled by applications that fail to properly validate server TLS/SSL
439 # setuid applications using libcurl
441 libcurl-using applications that set the 'setuid' bit to run with elevated or
466 When applications pass usernames, passwords or other sensitive data to