[10791] in bugtraq
Re: Windows NT 4.0, 95, 98 (?) networked PRN flaw
daemon@ATHENA.MIT.EDU (Aleph One)
Thu Jun 10 15:28:54 1999
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Message-Id: <19990610121119.W31644@underground.org>
Date: Thu, 10 Jun 1999 12:11:19 -0700
Reply-To: Aleph One <aleph1@UNDERGROUND.ORG>
From: Aleph One <aleph1@UNDERGROUND.ORG>
To: BUGTRAQ@NETSPACE.ORG
In-Reply-To: <375D5D50.538F22CB@nodc.noaa.gov>
This is a bug in the NFS server implementation. The NFS protocol
does not limit the character set that can be used in filenames, but
the NFS server MAY restrict it based on the native filesystem it
uses to store the files.
From RFC 1813:
4.6 File name component handling
Server implementations of NFS version 3 protocol will
frequently impose restrictions on the names which can be
created. Many servers will also forbid the use of names that
contain certain characters, such as the path component
separator used by the server operating system. For example,
the UFS file system will reject a name which contains "/",
while "." and ".." are distinguished in UFS, and may not be
specified as the name when creating a file system object.
The exact error status values return for these errors is
specified in the description of each procedure argument. The
values (which conform to NFS version 2 protocol server
practice) are not necessarily obvious, nor are they
consistent from one procedure to the next.
--
Aleph One / aleph1@underground.org
http://underground.org/
KeyID 1024/948FD6B5
Fingerprint EE C9 E8 AA CB AF 09 61 8C 39 EA 47 A8 6A B8 01
