Re: TI-H: linux...
[Prev][Next][Index][Thread]
Re: TI-H: linux...
We installed fortress at school (and are going to at work), and in order to
minimize the chance of soem BDU bypassing the startup files, you have t
change boot-up sequence (HD,A:,etc) and add
BootKeys=0
Autoscan=0
BootWarn=0
to the MSDOS.sys
BTW, if fortress is on a network macine, when the login prompt comes up hit
<CTRL><ESC> for your task manager.
and yes I do know how insecure it is afterwards too. If you use it in
conjunction with POLEDIT, then you make a mostly secure computer (sort of :)
)
David Knaack wrote:
> >From: sampablo2@juno.com (Sam Camp)
> >>Is that related to Fortress, the lockout software used on the Dells in
> >>my old
> >>school? It can be bypassed if you have Word installed. Just call up
> >>command.com via some simple Visual Basic for Applications coding.
> >
> >I don't know any thing about Foolproof, but hearing Fortress brings
> back
> >fond memories. You can also get by Fortress by sticking in one of
> those
> >win95 startup floppies, or breaking out to a DOS prompt while
> config.sys
> >is doing its thing.
>
> The first thing loaded in the config.sys at my school killed ability
> to break out of the load, very difficult (if not impossable) to break
> on the first line of config.sys. The solution was to hold down some
> keys during boot and force a keyboard failure, which on the IBM model
> 25's would dump you into dos, bypassing the startup files.
> I just carried around my boot floppy with all the network drivers tho,
> much easier :)
>
> DK
>
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.com
References: