Hi Dhanavel,

One of the first things that one notices when trying to set up IPsec is that
there are so many knobs and settings: even a pair of entirely
standards-conforming implementations sports a bewildering number of ways to
impede a successful connection. It's just an astonishingly-complex suite of
protocols.

One cause of the complexity is that IPsec provides mechanism, not policy:
rather than define such-and-such encryption algorithm or a certain
authentication function, it provides a framework that allows an
implementation to provide nearly anything that both ends agree upon.



IPsec would be nearly useless without the cryptographic facilities of
authentication and encryption, and these require the use of secret keys
known to the participants but not to anyone else.

The most obvious and straightforward way to establish these secrets is via
manual configuration: one party generates a set of secrets, and conveys them
to all the partners. All parties install these secrets in their appropriate
Security Associations in the SPD.

But this process does not scale well, nor is it always terribly secure: the
mere act of conveying the secrets to another site's SPD may well expose them
in transit. In a larger installation with many devices using the same
preshared key, compromise of that key makes for a very disruptive
re-deployment of new keys.

IKE — Internet Key Exchange — exists to allow two endpoints to properly set
up their Security Associations, including the secrets to be used. IKE uses
the ISAKMP (Internet Security Association Key Management Protocol) as a
framework to support establishment of a security association compatible with
both ends.

Multiple key-exchange protocols themselves are supported, with Oakley being
the most widely used. We'll note that IPsec key exchange typically takes
place over port 500/udp.


Regards,

T.Amardeep,

-- 
You received this message because you are subscribed to the Google Groups 
"nforceit" group.
To post to this group, send an email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/nforceit?hl=en-GB.

Reply via email to