Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!A.ISI.EDU!LYNCH From: LYNCH@A.ISI.EDU.UUCP Newsgroups: mod.protocols.tcp-ip Subject: Re: Access control and accountability Message-ID: <8704080341.AA20900@ucbvax.Berkeley.EDU> Date: Tue, 7-Apr-87 12:59:42 EST Article-I.D.: ucbvax.8704080341.AA20900 Posted: Tue Apr 7 12:59:42 1987 Date-Received: Sat, 11-Apr-87 03:35:31 EST References: Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 25 Approved: tcp-ip@sri-nic.arpa Hank, On the "system" side is is entirely up to the operating system that runs the hardware interface to the network. I have worked on a system that did enforce access controls on a per user basis to the network interfaces that were attached to it. Since the operating system allready had a strong notion of access control it was not dificult to add in the support for network access. But, it certainly is true that we needed the source code to everything in sight to make it all happen. The early days of networking had a notion of what it was that was being hooked up to the netowrk: a timesharing system with a responsible adminstration ensuring some kind of access restrictions or at least a place to call to register a complaint. Today's technological advances have made is so that everyone on earth is a "timesharing system administrator". Clearly the "responsibility" for hooking up to the network has to be placed elsewhere. The owner of the "cable" is teh obvious choice, but that does not take into account radio based networks... IN short: It looks like the "gateway owners" are going to have to become the administrators of the future! Yikes, back to the future??? Dan -------