There is quite a good explanation on page 348 of the Architecture / Admin
.pdf on the CD.

It's done by changing the content of the $FWDIR/lib/control.map file.  If
there are differing schemes specified on the firewall modules and the
management modules, the strongest wins, BUT, if one of the modules cannot
use that type of encryption the connection fails (so it pays to have either
a) consistant encryption settings or b) the same encryption licenses
deployed throughout).

As I said, the desciption in the book isn't bad, and there are a few
examples to clarify things.

Regards






[EMAIL PROTECTED]@lists.us.checkpoint.com on 29/09/2000 16:25:13

Sent by:  [EMAIL PROTECTED]


To:   [EMAIL PROTECTED]
cc:
Subject:  [FW1] Encryption levels and communication between mgmt and
      firewall mod ules



Hello Experts:

Can someone please tell me what type of encryption is used between the Mgmt
Module and Firewall module.

For instance, when pushing a policy down to a firewall, is the policy being
encrypted?  If so, how do you determine what type of encryption would be
used?  I do not see a setting to determine this.

Issue comes that if your management module has a DES key, but your firewall
module is licensed for 3DES.  Can you enable 3DES on your firewall module?
In the GUI, which connects to your Mgmt module, will you see any 3DES
options for your encryption types?

Steven M. Cantwell
Level 3 Support and Recreation
[EMAIL PROTECTED]





================================================================================

     To unsubscribe from this mailing list, please see the instructions at
               http://www.checkpoint.com/services/mailing.html
================================================================================





================================================================================
     To unsubscribe from this mailing list, please see the instructions at
               http://www.checkpoint.com/services/mailing.html
================================================================================

Reply via email to