xor ?????:
> On Friday 19 February 2010 11:25:26 VolodyA! V Anarhist wrote:
> > Also keep in mind contextual problems. A full stop '.', for example, is
> > allowed in Windows, but not if it's the last character in the file
> name (if
> > you have dual boot try to add . at the end of the filename in a real os,
> > and then open in in windows, it will tell you file doesn't exist.
> >
> > - Volodya
>
>
> Sure? To which windows' does this apply?
I'm on XP right now, and on my removable drive that i share between different
computers i can't read a directory that terminates with full stop. I've created
it under ubuntu on NTFS partition (because of course in specs nothing says that
it's illegal).
Basically it's a legacy of 8.3 file systems, for them *. means "any file
without
an extension). And the operating system strips the last '.' before trying to
access the file.
It would be interesting to create two files: "1" and "1." and see if the
attempted access to "1." would give me the contents of "1". This could lead to
some weird exploit things perhaps, as that is hardly an expected behaviour.
There are many inconsistancies when it comes to full stop under windows. For
example Windows explorer can have problems renaming files and directories that
start with a dot, although the rest of OS handle it fine now. Accessing them
doesn't have any issues that i have noticed.
- Volodya
--
http://freedom.libsyn.com/ Echo of Freedom, Radical Podcast
http://www.freedomporn.org/ Freedom Porn, anarchist and activist smut
"None of us are free until all of us are free." ~ Mihail Bakunin
