NAME

  SG_R_RFC3526_2 - [Responder Test]Transform payload SA Attributes check (3DES,SHA,PSK,DH5)   


TARGET

  SGW


SYNOPSIS

  SG_R_RFC3526_2.seq [-tooloption ...] -pkt SG_R_RFC3526_2.def -tooloption : v6eval tool option
See also ike_common.def and ike_ipsec.def and ike_addr.def and ike_pkt_ph1_recv.def and ike_pkt_ph2_recv.def


INITIALIZATION


TEST PROCEDURE

  This test check is following.

IDENTITY PROTECTION EXCHANGE
# Initiator(TN) Direction Responder(NUT) (1) HDR; SA ========>
(2) <======== HDR; SA Judgement (Check *1)
1. Send the first message from TN In the first message (1), the initiator generates a proposal it considers adequate to protect traffic for the given situation. The Security Association, Proposal, and Transform payloads are included in the Security Association payload (for notation purposes).
2. Receive the second message from NUT In the second message (2), the responder indicates the protection suite it has accepted with the Security Association, Proposal, and Transform payloads.


JUDGEMENT

        The first message must be accepted. And the second message must be returned.
        The second message Attributes(3DES:5,SHA:2,PSK:1,DH5:5) must be correct.
        And must conform to above Configuration.


TERMINATION

  Clean up SAD and SPD


REFERENCE

  RFC2409 
  4.Introduction

(omit)
IKE implementations MUST support the following attribute values:
-DES [DES] in CBC mode with a weak, and semi-weak, key check (weak and semi-weak keys are referenced in [Sch96] and listed in Appendix A). The key is derived according to Appendix B.
- MD5 [MD5] and SHA [SHA].
- Authentication via pre-shared keys.
- MODP over default group number one (see below).
In addition, IKE implementations SHOULD support: 3DES for encryption; Tiger ([TIGER]) for hash; the Digital Signature Standard, RSA [RSA] signatures and authentication with RSA public key encryption; and MODP group number 2. IKE implementations MAY support any additional encryption algorithms defined in Appendix A and MAY support ECP and EC2N groups.
(omit)

RFC3526 2. 1536-bit MODP Group
The 1536 bit MODP group has been used for the implementations for quite a long time, but was not defined in RFC 2409 (IKE). Implementations have been using group 5 to designate this group, we standardize that practice here.
The prime is: 2^1536 - 2^1472 - 1 + 2^64 * { [2^1406 pi] + 741804 }
Its hexadecimal value is:
FFFFFFFF FFFFFFFF C90FDAA2 2168C234 C4C6628B 80DC1CD1 29024E08 8A67CC74 020BBEA6 3B139B22 514A0879 8E3404DD EF9519B3 CD3A431B 302B0A6D F25F1437 4FE1356D 6D51C245 E485B576 625E7EC6 F44C42E9 A637ED6B 0BFF5CB6 F406B7ED EE386BFB 5A899FA5 AE9F2411 7C4B1FE6 49286651 ECE45B3D C2007CB8 A163BF05 98DA4836 1C55D39A 69163FA8 FD24CF5F 83655D23 DCA3AD96 1C62F356 208552BB 9ED52907 7096966D 670C354E 4ABC9804 F1746C08 CA237327 FFFFFFFF FFFFFFFF
The generator is: 2.


SEE ALSO

  perldoc V6evalTool
  IKE.html IKE Test Common Utility