RE: RFC: Illegal Characters in File Names

["Guy" <bugzilla@watkins-home.com>]

I vote you disallow no-printable characters!
0-31 and 127.
I have never seen a case where they are needed.  If some app wants to use
non-printable control characters, let the app change.

I have seen a case where the correct control characters cause the terminal
to change the cursor x,y position, then send the cursor x,y position back to
the computer and cause the user to log off.  The cursor was moved to the 4th
position, the response included a "ctrl D" (ascii 4).  Seems like a security
risk!

If someone used the above method, they may be able to cause a simple "ll"
command to cause another program to be run!

Maybe we should ask:
Is there a good reason to support these control characters?
For now, assume that "because we do now" is not a good reason.

Guy

-----Original Message-----
From: linux-fsdevel-owner@vger.kernel.org
[mailto:linux-fsdevel-owner@vger.kernel.org] On Behalf Of Joseph D. Wagner
Sent: Tuesday, July 20, 2004 12:25 PM
To: 'Jan Hudec'
Cc: linux-fsdevel@vger.kernel.org
Subject: RE: RFC: Illegal Characters in File Names

> Read the list again, please. Ebcdic is included there.

OK, that was an oversimplification, but guess what?  They are all still
non-printing control characters with the exception of 127.

Joseph D. Wagner

-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html