Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security ISSForum
[Top] [All Lists]

[ISSForum] Proventia M MessageWall configuration

Subject: [ISSForum] Proventia M MessageWall configuration
Date: Tue, 23 Aug 2005 18:50:10 -0500
Hi all:



Below are the first seven lines of the default Messagewall configuration
file taken from a Proventia M10.



processes=2

max_clients=5

max_backends=5

max_per_ip=5

max_message_size=10485760

max_rcpt=25

max_ext_rcpt=25



Again below is part of the sample configuration file that comes with the
firmware



# This is the MessageWall sample configuration file.  All

# variables in this file must be uncommented and defined before

# MessageWall will start.

#

#

# The number of processes to create at startup.  This option is

# provided to fully utilize machines with multiple processors;

# it should never be set higher than the number of processors in

# your system.  Several of the scaling variables (max_clients,

# max_backends, max_per_ip) are per process.

#

processes=2

#

#

# XXXX max_clients needs to be equal to max_backends if multi_backend!=0

#

# The maximum number of clients that messagewall should accept

# per process.  Any clients attempting to connect over this limit

# will receive a temporary error instead of a greeting.

#

max_clients=5

#

#

# The number of connections to the backend server to try to keep

# open per process.  If no connections are free when we receive

# a message from a client, MessageWall sends the client a temporary

# error indicating that they should try again later.

#

max_backends=5

#

#

# The number of client connections to accept from a certain IP per

# process.  Any clients attempting to connect that would go over

# this limit are sent a temporary error instead of a greeting.  This

# is a security measure to prevent one user from overwhelming the

# server; it should be set to a small fraction of max_clients

# so that many IPs would be required to deny access to the server.

#

#max_per_ip=5

max_per_ip=5

#

#

# The maximum size, in bytes, of message to accept.  This size is

# announcing in the ESMTP SIZE parameter, and messages larger than

# this size are refused.

#

max_message_size=10485760

#

#

# The maximum number of recipients for a given message.  According to

# RFC 2821, this should be at least 100.  It is usually practical,

# however, to keep it much smaller than this.  Users trying to send

# to more recipients will receive a permanent error.

#

max_rcpt=25

#

# The maximum number of recipients for a given message from an

# external MTA.  According to RFC 2821, this should be at least 100.

# It is usually practical, however, to keep it much smaller than this.

# Users trying to send to more recipients will receive a permanent

# error. This parameter should be less than or equal to max_rcpt.



max_ext_rcpt=25



As you can read in the block marked in red, the processes parameter should
be set to 1 (one) when the equipment has one procesor. However as shown in
the default configuration file (first seven lines) the parameter is always
set to 2 (two).



Now, my question: ¿What is correct?, and why?



This is very important because it affects the RAM memory allocation when
changing  max_clients and/or max_backends parameters.



An answer will be much appreciated.



Thanks and Regards



epo



_______________________________________________
ISSForum mailing list
ISSForum@iss.net

TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to 
https://atla-mm1.iss.net/mailman/listinfo/issforum

To contact the ISSForum Moderator, send email to mod-issforum@iss.net

The ISSForum mailing list is hosted and managed by Internet Security Systems, 
6303 Barfield Road, Atlanta, Georgia, USA 30328.

<Prev in Thread] Current Thread [Next in Thread>