I know it is not a good idea to put a server on the net, but sometimes it is the best solution for a client to access this server from a remote site via telnet with print servers and workstations. Looking for suggestions on what services to stop (/etc/services) and or (/etc/inetd.conf) or both, and what to allow and what security level to run, at the same time keeping simple enough for the end users to logon. Any tips, pointers and suggestions are highly apreciated. Thank you all.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Advice on securing an SCO openserver on a public IP
- Thread starter spddmon
- Start date
Megabitman
MIS
You're right, it's a lousy idea and personally, I'd setup a VPN for the remote site and hide both systems behind a NAT router. This is especially true since VPN routers are all the rage and (as much as I dislike LinkSys) inexpensive. If you really want to know how many people are lurking out there probing all the various ports available (and they have automated software to do the probing), setup a windows box with Black Ice (or something similar) and watch the number of attempts which are made on a public address. But, it's just my opinion.
- Status
Similar threads
- Locked
- Question