eljazzar@utkux1.utk.edu (Mohamad El Jazzar) (04/10/91)
Hello, I need to set up a guest account that would be accessible only if the user is using the local machine, i.e., I don't want users from outside to be able to log on to it (telnet, rsh, rlogin, the works..). There is a catch to this: if the user has a window to another system, and wanted to rsh or rlogin back to the NeXT, he should be allowed to do so (although this is "across the net" access, we still want this functionality for the local user). More details: We recently (finally) got a NeXT Station in our department, and I was asked to set it up following a pattern similar to other workstations that we maintain. This includes mounting volumes off of a central server which is also an NIS server. The User Services Staff in the Computing Center expressed the need for a "Guest" account, which should be fully functional. At the same time, our group figured that allowing access to such an account could jeopardize the security of our systems, in addition to possibly "over-using" the resources that would be available to it. At first thought, I thought that changing the guest's shell to another front -end shell would be a good idea. This shell would check if the user is logging in from the actual machine or across the net. This scheme (sort of) worked, but then this same user could not login at the NeXT prompt. (After entering the username and password, I get a message back saying something to the effect that another shell will be run, and that the output will be ignored, and when I confirm, the prompt comes back staring at me.) Ideas anyone?? (Thanks) -------------------------------------------------------------------- Mohamad El Jazzar Internet: eljazzar@utkux1.utk.edu U. of Tenn. Computing Center BITNET: eljazzar@utkvx Knoxville, Tennessee