*BSD News Article 9216


Return to BSD News archive

Received: by minnie.vk1xwt.ampr.org with NNTP
	id AA5395 ; Wed, 23 Dec 92 19:00:15 EST
Xref: sserve comp.protocols.tcp-ip:21143 comp.unix.bsd:9273
Newsgroups: comp.protocols.tcp-ip,comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!zaphod.mps.ohio-state.edu!caen!mtu.edu!tony
From: tony@mtu.edu (Tony Dal Santo)
Subject: Re: Limiting Telnet access.
Message-ID: <1992Dec21.211508.9555@mtu.edu>
Organization: Michigan Technological University
References: <1992Dec17.230214.16501@vector.dallas.tx.us>
Date: Mon, 21 Dec 1992 21:15:08 GMT
Lines: 20

tbo@vector.dallas.tx.us (Terry Bohaning) writes:
>I've recently become very concerned about the security of many of 
>the Unix workstations under my care. Some of the users are overly
>free with their passwords and I would really like to limit access
>to the systems.

Along these lines, I am curious if anyone has an idea how to allow
certain users access to the network, and deny others.  Something
like putting the user in group "network" to grant them access.  By
access, I mean system call level access like socket().  Even better
would be to provide a list of addresses/networks that are restricted/
allowed.

I imagine with a streams implementation of tcp/ip, you could change
the perms on /dev/ip or /dev/tcp.

Does anyone have any utilities for tracing a TCP port to a process number?

Tony Dal Santo
tony@mtu.edu