Lines Matching full:applications

24 Many applications are used in closed networks where users and servers can
27 some risks in the ways in which applications commonly use libcurl and
29 classes of attacks that robust applications should consider. The Common
54 For applications that enable .netrc use, a user who manage to set the right
104 enabled by default. Applications may opt to restrict that set further.
130 Applications can mitigate against this by disabling
156 10.1.2.3. Applications can mitigate against this by setting a
164 and display the result. Applications can mitigate against this with the
170 behind a firewall. Applications can mitigate against this by using the
209 overwritten. Applications must not allow any unsanitized URL to be passed in
211 uploads. Instead, the applications should consider handling redirects itself,
217 information to be sent to an unknown second server. Applications can mitigate
236 **http://mail.example.com/delete-stuff.cgi?delete=all** Applications can
246 Applications must not allow unsanitized SCP: URLs to be passed in for
261 applications to disable it, to establish a connection to another host over the
266 order to protect applications for inadvertent probes of for example internal
287 Applications may find it tempting to let users set the URL that it can work
377 this. Instead, applications should monitor the amount of data received within
407 enabled by applications that fail to properly validate server TLS/SSL
430 # setuid applications using libcurl
432 libcurl-using applications that set the 'setuid' bit to run with elevated or
457 When applications pass user names, passwords or other sensitive data to