Why not a private news server?

Squash realsquash at yahoo.com
Mon Nov 29 19:23:13 GMT 1999


--- David Cooley <n5xmt at bellsouth.net> wrote:
> They find out what IP addresses respond to pings,
> then run port scans on 
> the addresses found.
> 
> They can then determine if that IP supports web,
> NNTP, SMTP etc.
> If a news server is protected by a password, they
> have crack programs that 
> throw usernames/passwords at the systems.  Systems
> also have backdoors put 
> in by the software authors.  Spammers/hackers know
> these back doors and use 
> them.

If they go through all this then they deserve to get
in!   Seriously, if the admin(s) know what they are
doing, back doors are closed and spammers are filtered
out.

> And that is what I am interested in as well, but 2
> or 3 of the group want 
> to badmouth public email servers for a *TEMPORARY*
> home.  If the interest 
> is really to keep the list etc going, then *ANY*
> options should be considered.

I second that.

> function.  I'm having 
> that problem right now with a webserver.
> Our company sold one and stated it's limit was 200
> concurrent users.  We are only at 50 concurrent 
> users and the machine cannot keep up.  It's got 4 
> Pentium III/600 MHZ CPU's, 2G ram and 100G hard
> drive space (All ultra Wide  SCSI2).  Network 
> connection is via OC-12 622MB/sec fiber.

Just because your big server has problems doesn't mean
every server like yours is going to have the same
problems.  What is the problem?  Bandwidth?  CPU
power?  Not likely.  OS?  Likely.  What type of load
is it?  Is it all CGI?  Is it a WWW server?  Does it
interface to a legacy DB system?  

I've gone through the server sizing thing so many
times it's not funny.

Squash
__________________________________________________
Do You Yahoo!?
Thousands of Stores.  Millions of Products.  All in one place.
Yahoo! Shopping: http://shopping.yahoo.com



More information about the Gmecm mailing list