12 Dec
2011
12 Dec
'11
8:05 p.m.
On Mon, Dec 12, 2011 at 5:44 PM, Fred Cisin <cisin at xenosoft.com> wrote:
On Mon, 12 Dec 2011, Guy Sotomayor wrote:
people from
tampering with a file by embedding an 0xFF character in the
name... perfectly legal name, but appears in a DIR listing as a space.
One of those security-through-obscurity things.
It's even more general than that. Many folks
have fallen into the
Microsoft (FAT) limitation that a file is [char]+.[char][char][char]
format for a file name.
char[char][char][char][char][char][char][char](.)[char][char][char]
There MUST be at least one character at the beginning of the filename. The
remaining 7 positions, and the three of the "extension" are padded out
with spaces if not used, and no non-space character can FOLLOW a space in
either field ("undefined" behavior results from embedded spaces (F 3.C)),
although the command line parser will treat any spaces in the command
line as delimiters. (It will assume that FILENAM .C or F 3.C are each two
items, not single names.)
Microsoft (Patterson) lifted THAT directly from CP/M.
Who did Gary Kildall lift it from?
I'm reminded of an old trick from the days of DOS 3.2... keep