Xref: utzoo comp.sys.ibm.pc:48419 alt.msdos.programmer:1479
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!pt.cs.cmu.edu!b.gp.cs.cmu.edu!Ralf.Brown@B.GP.CS.CMU.EDU
From: Ralf.Brown@B.GP.CS.CMU.EDU
Newsgroups: comp.sys.ibm.pc,alt.msdos.programmer
Subject: Re: Hiding/Protecting Directories
Message-ID: <26231896@ralf>
Date: 11 Apr 90 11:44:22 GMT
Sender: ralf@b.gp.cs.cmu.edu
Organization: Carnegie Mellon University School of Computer Science
Lines: 27
In-Reply-To: <1990Apr11.052529.20474@msuinfo.cl.msu.edu>

In article <1990Apr11.052529.20474@msuinfo.cl.msu.edu>, draper@cpsin1.uucp (Patrick J Draper) wrote:
}>       Does anyone know of a way of passowrd protecting a directory and
}>it's contents?
}
}Something that will give people a really hard time is to use Turbo
}Pascal (other languages might work too) to create a directory with a
}funny name that dos doesn't understand from the command line like
}#&% 123  ---- the space between the % and the 1 is intentional. The 
}idea is that you can use a little program to change your directories.
}What's really neat is that on a dos directory listing, the characters
}you use after the space will not be displayed, so there's added

Maybe on your version, but MSDOS 3.3 COMMAND.COM, 4DOS v3.0, SD v6.2, PiCnix
v3 "ls" and the PC Tools v5.5 Shell all display the characters after the blank
(I just tried it, doing a MKDIR `T 2` with 4DOS).

}security. They can't see the full name of the directory, and even if
}they could, there's no legal way they can specify that directory on a
}command line.

Unless they are using 4DOS or the PiCnix utilities or PC Tools or ....
--
UUCP: {ucbvax,harvard}!cs.cmu.edu!ralf -=- 412-268-3053 (school) -=- FAX: ask
ARPA: ralf@cs.cmu.edu  BIT: ralf%cs.cmu.edu@CMUCCVMA  FIDO: Ralf Brown 1:129/46
"How to Prove It" by Dana Angluin              Disclaimer? I claimed something?
21. proof by ghost reference:  Nothing even remotely resembling the cited
    theorem appears in the reference given.