Xref: utzoo comp.dcom.lans:2054 comp.protocols.tcp-ip:5621 Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!unmvax!ncar!ames!oli-stl!asylum!romkey From: romkey@asylum.sf.ca.us (John Romkey) Newsgroups: comp.dcom.lans,comp.protocols.tcp-ip Subject: Re: Network Security Keywords: network security virus Message-ID: <1009@asylum.sf.ca.us> Date: 30 Nov 88 04:08:09 GMT References: <26314@bu-cs.BU.EDU> Reply-To: romkey@asylum.UUCP (John Romkey) Organization: The Asylum; Belmont, CA Lines: 19 In article <26314@bu-cs.BU.EDU> kwe@bu-cs.BU.EDU (kwe@bu-it.bu.edu (Kent W. England)) writes: > Networks are secure when they operate properly. I'm going to pick a nit. You're automagically defining what "operate properly" means here. I don't think it's a truism that a network that operates properly is secure. You might quite happily build a small network that's not connected to any other networks that has no security and be quite happy with it - it's operating properly without security and there's no need for security (actually, here isolation is a form of security). A network that is conformant with current TCP/IP specifications is not necessarily secure but does operate properly. -- - john romkey romkey@asylum.uucp romkey@xx.lcs.mit.edu romkey@asylum.sf.ca.us Find the cost of freedom, buried in the ground Mother Earth will swallow you, lay your body down.