Changeset 1188

Timestamp:

Mar 14, 2011, 2:06:53 PM (8 years ago)

Author:

julian.reschke@…

Message:

rephrase the considerations about path handling in filenames (Stewart Bryant's DISCUSS)

Location:

draft-ietf-httpbis-content-disp/latest

Files:

• draft-ietf-httpbis-content-disp.html (modified) (3 diffs)
• draft-ietf-httpbis-content-disp.xml (modified) (3 diffs)

draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.html

@@ -633 +633 @@
       <ul>
          <li>
-            <p>When the value contains path separator characters ("\" or "/"), recipients <em class="bcp14">SHOULD</em> ignore all but the last path segment (the actual filename). This prevents overwriting of well-known file system locations
-               (such as "/etc/passwd").
+            <p>Recipients <em class="bcp14">MUST NOT</em> be able to write into any location other than one to which they are specifically entitled. To illustrate the problem consider
+               the consequences of being able to overwrite well-known system locations (such as "/etc/passwd"). One strategy to achieve this
+               is to never trust folder name information in the filename parameter, for instance by stripping all but the last path segment
+               and only consider the actual filename (where 'path segment' are the components of the field value delimited by the path separator
+               characters "\" and "/").
             </p>
          </li>
@@ -718 +721 @@
       <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;Acknowledgements
       </h1>
-      <p id="rfc.section.9.p.1">Thanks to Adam Barth, Rolf Eike Beer, Bjoern Hoehrmann, Alfred Hoenes, Roar Lauritzsen, Henrik Nordstrom, and Mark Nottingham
-         for their valuable feedback.
+      <p id="rfc.section.9.p.1">Thanks to Adam Barth, Stewart Bryant, Rolf Eike Beer, Bjoern Hoehrmann, Alfred Hoenes, Roar Lauritzsen, Henrik Nordstrom,
+         and Mark Nottingham for their valuable feedback.
       </p>
       <h1 id="rfc.references"><a id="rfc.section.10" href="#rfc.section.10">10.</a> References
@@ -1026 +1029 @@
       </ul>
       <h2 id="rfc.section.E.12"><a href="#rfc.section.E.12">E.12</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-content-disp-07</a></h2>
-      <p id="rfc.section.E.12.p.1">Clarify that by "last path segment" we mean the actual filename.</p>
+      <p id="rfc.section.E.12.p.1">Rephrase the requirement about well-known file system locations, and also clarify that by "last path segment" we mean the
+         actual filename.
+      </p>
       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
       <p class="noprint"><a href="#rfc.index.C">C</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.R">R</a> 

draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml

@@ -252 +252 @@
   <list style="symbols">
     <x:lt><t>
-      When the value contains path separator characters ("\" or "/"),
-      recipients &SHOULD; ignore all but the last path segment (the actual
-      filename). This prevents overwriting of well-known file system locations
-      (such as "/etc/passwd").
+      Recipients &MUST-NOT; be able to write into any location other than one
+      to which they are specifically entitled. To illustrate the problem
+      consider the consequences of being able to overwrite well-known system
+      locations (such as "/etc/passwd"). One strategy to achieve this is to
+      never trust folder name information in the filename parameter, for
+      instance by stripping all but the last path segment and only consider the
+      actual filename (where 'path segment' are the components of the field
+      value delimited by the path separator characters "\" and "/").
     </t></x:lt>
     <x:lt><t>
@@ -416 +420 @@
 <section title="Acknowledgements">
 <t>
-  Thanks to Adam Barth, Rolf Eike Beer, Bjoern Hoehrmann, Alfred Hoenes, Roar Lauritzsen,
-  Henrik Nordstrom, and Mark Nottingham for their valuable feedback.
+  Thanks to Adam Barth, Stewart Bryant, Rolf Eike Beer, Bjoern Hoehrmann,
+  Alfred Hoenes, Roar Lauritzsen, Henrik Nordstrom, and Mark Nottingham for
+  their valuable feedback.
 </t>
 </section>  
@@ -1053 +1058 @@
 <section title="Since draft-ietf-httpbis-content-disp-07" anchor="changes.since.07">
 <t>
-  Clarify that by "last path segment" we mean the actual filename.
+  Rephrase the requirement about well-known file system locations, and also
+  clarify that by "last path segment" we mean the actual filename.
 </t>
 </section>