Rollup merge of #125060 - ChrisJefferson:pathbuf-doc, r=workingjubilee

Expand documentation of PathBuf, discussing lack of sanitization

Various methods in `PathBuf`, in particular `set_file_name` and `set_extension` accept strings which include path seperators (like `../../etc`). These methods just glue together strings, so you can end up with strange strings.

This isn't reasonable to change/fix at this point, and might not even be fixable, but I think should be documented. In particular, you probably shouldn't blindly build paths using strings given by possibly malicious users.
This commit is contained in:
Stuart Cook 2024-09-12 20:37:14 +10:00 committed by GitHub
commit 8e037ccec7
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -1153,6 +1153,21 @@ impl FusedIterator for Ancestors<'_> {}
/// ``` /// ```
/// ///
/// Which method works best depends on what kind of situation you're in. /// Which method works best depends on what kind of situation you're in.
///
/// Note that `PathBuf` does not always sanitize arguments, for example
/// [`push`] allows paths built from strings which include separators:
///
/// use std::path::PathBuf;
///
/// let mut path = PathBuf::new();
///
/// path.push(r"C:\");
/// path.push("windows");
/// path.push(r"..\otherdir");
/// path.push("system32");
///
/// The behaviour of `PathBuf` may be changed to a panic on such inputs
/// in the future. [`Extend::extend`] should be used to add multi-part paths.
#[cfg_attr(not(test), rustc_diagnostic_item = "PathBuf")] #[cfg_attr(not(test), rustc_diagnostic_item = "PathBuf")]
#[stable(feature = "rust1", since = "1.0.0")] #[stable(feature = "rust1", since = "1.0.0")]
pub struct PathBuf { pub struct PathBuf {
@ -1391,6 +1406,9 @@ pub fn pop(&mut self) -> bool {
/// `file_name`. The new path will be a sibling of the original path. /// `file_name`. The new path will be a sibling of the original path.
/// (That is, it will have the same parent.) /// (That is, it will have the same parent.)
/// ///
/// The argument is not sanitized, so can include separators. This
/// behaviour may be changed to a panic in the future.
///
/// [`self.file_name`]: Path::file_name /// [`self.file_name`]: Path::file_name
/// [`pop`]: PathBuf::pop /// [`pop`]: PathBuf::pop
/// ///
@ -1411,6 +1429,12 @@ pub fn pop(&mut self) -> bool {
/// ///
/// buf.set_file_name("baz"); /// buf.set_file_name("baz");
/// assert!(buf == PathBuf::from("/baz")); /// assert!(buf == PathBuf::from("/baz"));
///
/// buf.set_file_name("../b/c.txt");
/// assert!(buf == PathBuf::from("/../b/c.txt"));
///
/// buf.set_file_name("baz");
/// assert!(buf == PathBuf::from("/../b/baz"));
/// ``` /// ```
#[stable(feature = "rust1", since = "1.0.0")] #[stable(feature = "rust1", since = "1.0.0")]
pub fn set_file_name<S: AsRef<OsStr>>(&mut self, file_name: S) { pub fn set_file_name<S: AsRef<OsStr>>(&mut self, file_name: S) {