Xref: utzoo comp.dcom.lans:2124 comp.periphs:1393 comp.terminals:1005 Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!haven!uflorida!gatech!hubcap!ncrcae!ncrlnk!uunet!wucs1!wuphys!wucfua!wubios!phil From: phil@wubios.wustl.edu (J. Philip Miller) Newsgroups: comp.dcom.lans,comp.periphs,comp.terminals Subject: Re: Terminal Servers? Summary: and what about security Message-ID: <280@wubios.wustl.edu> Date: 20 Dec 88 03:27:52 GMT References: <147@iquery.UUCP> <12380@cup.portal.com> <689@hscfvax.harvard.edu> <442@maxim.ERBE.SE> Reply-To: phil@wubios.UUCP (J. Philip Miller) Organization: Washington University (St. Louis) Lines: 14 In article <442@maxim.ERBE.SE> prc@maxim.ERBE.SE (Robert Claeson) writes: rutgers.edu (Ron Natalie) writes: >> Both Bridge and Cisco terminal servers will boot either from themselves >> (Bridge uses a floppy, cisco uses roms (look ma! no moving parts) or over >> the network. > >The Annex terminal servers will boot over the network from either a computer >or from another Annex. and what about the security implications when these devices reboot over the network? What keeps some charlatan from providing an "improved" set of definitions which destroys any secuity constraints which you have carefully provided? Forcing a device to reboot is frequently the easiest threat to execute.