From: Cody P Schafer <cody@linux.vnet.ibm.com>
To: Marian Beermann <public@enkore.de>
Cc: linux-fsdevel@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] NTFS code doesn't sanitize folder names sufficiently
Date: Wed, 01 Aug 2012 16:16:01 -0700 [thread overview]
Message-ID: <5019B8B1.7090902@linux.vnet.ibm.com> (raw)
In-Reply-To: <501189DA.4030709@enkore.de>
> The solution to this would be to disallow creation of files and
> folders on NTFS drives containing illegal characters.
Illegal characters with respect to Windows & the like are different
from Illegal characters with respect to the NTFS filesystem structure.
Looking at ntfs-3g(8) [yes, I'm aware that is a different driver that
this bug is about], the section on Windows Filename Compatability says
this:
[...] all characters are
allowed except '/' and '\0'. This is perfectly legal on Windows,
though some application may get
confused. The option windows_names may be used to apply Windows
restrictions to new file names.
To recap: no data will be lost due to using '\' in filenames. Some
operating systems just may not be capable off accessing it.
--
Cody
prev parent reply other threads:[~2012-08-01 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 18:18 [BUG] NTFS code doesn't sanitize folder names sufficiently Marian Beermann
2012-07-27 14:28 ` Calvin Walton
2012-08-01 23:16 ` Cody P Schafer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5019B8B1.7090902@linux.vnet.ibm.com \
--to=cody@linux.vnet.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=public@enkore.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).