Xref: utzoo news.newusers.questions:2731 comp.dcom.lans:5855 news.sysadmin:3271 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!uwvax!rang From: rang@cs.wisc.edu (Anton Rang) Newsgroups: news.newusers.questions,comp.dcom.lans,news.sysadmin Subject: Re: Why & how to join Internet community? Message-ID: Date: 7 Sep 90 00:45:44 GMT References: <1990Aug29.040844.25685@msuinfo.cl.msu.edu> <1990Aug29.054812.8000@ux1.cso.uiuc.edu> Sender: news@spool.cs.wisc.edu Organization: UW-Madison CS department Lines: 23 In-reply-to: gupta@ux1.cso.uiuc.edu's message of 29 Aug 90 05:48:12 GMT In article <1990Aug29.054812.8000@ux1.cso.uiuc.edu> gupta@ux1.cso.uiuc.edu (Rohit Gupta) writes: >jes@mth.msu.edu (Jesse) writes: >>Possible answer : Use telnet/ftp. >> While telnet/ftp is convenient, it's not so important to a >> company unless you need to use remote computation substantially. > >Another reason why a company may not prefer a TCP/IP connection is because >of security. With telnet someone could try to login to your system. With ftp >he/she could try to steal some files. If you have a smart gateway, you can configure it to refuse incoming TCP/IP connections to certain ports. (Bellcore does this, for instance.) Alternatively, run a dumb gateway but don't allow direct TCP/IP to hosts other than the gateway; this will make it considerably more difficult for people to break into your company. (If I've missed something here, someone is bound to point it out. :-) Anton +---------------------------+------------------+-------------+ | Anton Rang (grad student) | rang@cs.wisc.edu | UW--Madison | +---------------------------+------------------+-------------+