On Thu, 10 Jan 2002, Steve and Steven (back-and-forth, with an occasional insertion by Glenn)..<g>.. wrote:
--------------snip---------------- >> As you get into Linux more, you'll discover the desire >> to run servers... possibly a web server, or maybe an ftp >> server, or how about a simple news server. Maybe allow >> friends to log onto your machine using ssh, or hie back >> to bygone days by running a gopher server. ;-) >>> And then explain what it is that the "average user" would be >>> thowing away by not using those sevices ? -------------snip------------------- > How is someone else going to access my machine > through *only* my print server? > their buffer overflow at port 515, and that gains them > access (assuming it's not firewalled). > As root, do a few netstats to see if you perhaps > have more listening processes than you're aware of. > (at one point, even the X server was vulnerable to > being "eavesdropped" on... your desktop could have > been visible on others' computers) > # netstat -upant > # netstat -l > # netstat --------------snip--------------- > Well, there you go. It would seem my part in this > conversation has been obviated. --------------snip------------- > - Steve No, Steve....we don't want this discussion to end here... You are making valid points...Steven is making valid points...Glenn is making valid points. Why this may be important is because more of us are moving over into Linux (even I am timidly dipping my widdow toes into the water) and if we do NOT identify the possibilities for infestation, this list COULD turn into a "my linux box is broke" complaints-board. I do NOT ever intend to run those extra services, either...at least not until I am WAY more experienced...but this apparently does not definitely protect me from crackers...so... 1. Let us try to generally identify the main problem areas 2. Get some cut-and-dried instructions for newbies to do to their installs, immediately, before they put it on the net. 3. These should include those ISTAT checks....one question I have is how do I automagically enable these checks on every boot, so I can be SURE everything is shut down, etc. 4. How do we identify just WHAT threats we are likely to be opened to. That should be a start...<g g g>....and don't give up the ship, just because we all (or any one of us, over any single point) don't see HOW we could be affected (and infected). Now, I'm like Glenn....I have set up an absolutely INVULNERABLE box.. ...but...my years of experience tell me this ain't ever so....so.. I'd like you to stay with it for a few more passes.. Thanks ....gregy -- This mail was written by user of Arachne, the Ultimate Internet Client
