[GNUnet-SVN] [gnurl] 71/150: libcurl-security.3: separate file:// section

[gnunet]

This is an automated email from the git hooks/post-receive script.

ng0 pushed a commit to branch master
in repository gnurl.

commit 63f6b3b22077c6fd4a75ce4ceac7258509af412c
Author: Daniel Stenberg <address@hidden>
AuthorDate: Tue Feb 13 14:04:04 2018 +0100

    libcurl-security.3: separate file:// section
    
    ... just to make it more apparent. Even if it repeats
    some pieces of information.
---
 docs/libcurl/libcurl-security.3 | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docs/libcurl/libcurl-security.3 b/docs/libcurl/libcurl-security.3
index 185fb6b08..377301ee0 100644
--- a/docs/libcurl/libcurl-security.3
+++ b/docs/libcurl/libcurl-security.3
@@ -208,6 +208,13 @@ of how the SCP protocol is designed. e.g.
 
 Applications must not allow unsanitized SCP: URLs to be passed in for
 downloads.
+.SH "file://"
+By default curl and libcurl support file:// URLs. Such a URL is always an
+access, or attempted access, to a local resource. If your application wants to
+avoid that, keep control of what URLs to use and/or prevent curl/libcurl from
+using the protocol.
+
+By default, libcurl prohibits redirects to file:// URLs.
 .SH "What if the user can set the URL"
 Applications may find it tempting to let users set the URL that it can work
 on. That's probably fine, but opens up for mischief and trickery that you as

-- 
To stop receiving notification emails like this one, please contact
address@hidden