");
#======================================================================
vStop($IF1);
vStop($IF0);
ikeReset();
ikeExitPass();
#NOTREACHED
######################################################################
__END__
=head1 NAME
SG_R_A_RFC2409_5_5 - [Responder Test]Implementation of Aggressive Mode with pre-shared key check
=head1 TARGET
SGW
=head1 SYNOPSIS
=begin html
SG_R_A_RFC2409_5_5.seq [-tooloption ...] -pkt SG_R_A_RFC2409_5_5.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
=end html
=head1 INITIALIZATION
=begin html
HOST-2(TN)
|3ffe:501:ffff:104::11
|
Net-v --+------------------------+-------- 3ffe:501:ffff:104::/64
|
|
SGW-2(TN):initiator
|3ffe:501:ffff:103::11
|
Net-w --+--------+------------------------ 3ffe:501:ffff:103::/64
|
|
ROUTER-2(TN)
| 3ffe:501:ffff:102::11
|
Net-x --+--------+------------------------ 3ffe:501:ffff:102::/64
|
|3ffe:501:ffff:102::1
SGW-1(NUT):responder
|3ffe:501:ffff:101::1
|
Net-y --+--------+------------------------ 3ffe:501:ffff:101::/64
|
| 3ffe:501:ffff:101::11
ROUTER-1(TN)
|
|
Net-z -----------+---------------+-------- 3ffe:501:ffff:100::/64
|
|3ffe:501:ffff:100::13
HOST-1(TN)
Verification Points
Implementation of Aggressive Mode with pre-shared key check.
Configuration
Initiator and Responder IKE parameter
At least, following parameter must be included in proposal.
| Machine |
Src |
Dest |
Phase I |
Phase II |
| Ex mode |
Key Value |
Enc Alg |
Hash Alg |
Auth Method |
DH Group |
PH1 Lt |
IDx |
Proto ID |
Trans ID |
Mode |
Auth Alg |
PH2 Lt |
IDci |
IDcr |
Upper |
| SGW-1 |
SGW-1 addr |
SGW-2 addr |
Aggressive |
IKE-TEST |
3DES |
SHA |
pre-shared key |
2 |
8 Hour |
SGW-1 addr |
PROTO_IPSEC_ESP |
ESP_3DES |
Tunnel |
HMAC-SHA |
8 Hour |
Net-v addr |
Net-z addr |
any |
| SGW-2 |
SGW-2 addr |
SGW-1 addr |
Aggressive |
IKE-TEST |
3DES |
SHA |
pre-shared key |
2 |
8 Hour |
SGW-2 addr |
PROTO_IPSEC_ESP |
ESP_3DES |
Tunnel |
HMAC-SHA |
8 Hour |
Net-v addr |
Net-z addr |
any |
*Ex Mode = Exchange mode
*IDx = identity payload
*IDci = identity payload
*IDcr = identity payload
*Enc Alg = IKE Encryption Algorithm
*Hash Alg = IKE Authentication Algorithm
*Key Value = pre-shared key value
*PH1 Lt = Phase-1 Lifetime
*PH2 Lt = Phase-2 Lifetime
*Proto ID = Protocol Identifier
*Trans ID = Transform Identifier
*Mode = Encapsulation Mode
*Auth Alg = Authentication Algorithm
*Auth Method = Authentication Method
*DH Group = Diffie-Hellman Group
*Upper = Upper Layer Protocol
*SGW-1 addr = SGW-1 address
*SGW-2 addr = SGW-2 address
*Net-z = Net-z network address
*Net-v = Net-v network address
=end html
=head1 TEST PROCEDURE
=begin html
This test check is following.
AGGRESSIVE EXCHANGE
# Initiator(TN) Direction Responder(NUT)
(1) HDR; SA, KE, Ni, IDii ========>
(2) <======== HDR; SA, KE, Nr, IDir, HASH_R
Judgement (Check *1)
(3) HDR[*]; HASH_I ========>
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).
Keying material used to arrive at a common shared secret and random
information which is used to guarantee liveness and protect against
replay attacks are also transmitted. Additionally, the initiator
transmits identification information.
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.
Keying material used to arrive at a common shared secret and random
information which is used to guarantee liveness and protect against
replay attacks is also transmitted.Additionally, the responder
transmits identification information and the results of the agreed
upon authentication function(hash function).
3. Send the third message from TN
In the third (3) message, the initiator send the results of the
agreed upon authentication function(hash function).
* PHASE II
QUICK MODE
# Initiator(TN) Direction Responder(NUT)
(1) HDR*, HASH(1),
SA, Ni ========>
(2) <======== HDR*, HASH(2), SA, Nr
Judgement (Check *2)
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).
And initiator send HASH(1) and Nonce. HASH(1) is the prf over the
message id (M-ID) from the ISAKMP header concatenated with the entire
message that follows the hash including all payload headers,
but excluding any padding added for encryption. Nonce is random
information which is used to guarantee liveness.
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. And responder send HASH(2) and Nonce.
HASH(2) is identical to HASH(1) except the initiator's nonce-- Ni,
minus the payload header-- is added after M-ID but before the
complete message. Nonce is random
information which is used to guarantee liveness.
=end html
=head1 JUDGEMENT
In Phase I, the first to the third message must be exchanged correctly.
Check *1
Security Association, Key Exchange, Nonce, Identification, Hash Payload Format must be base on description of RFC.
And ISAKMP SA must be established.
In Phase II,the first message must be accepted.
And the second message is returned.
Check *2
NUT must send second message with ISAKMP SA.
And must conform to above Configuration.
=head1 TERMINATION
Clean up SAD and SPD
=head1 REFERENCE
=begin html
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).
(omit)
5. Exchanges
There are two basic methods used to establish an authenticated key
exchange: Main Mode and Aggressive Mode. Each generates authenticated
keying material from an ephemeral Diffie-Hellman exchange. Main Mode
MUST be implemented; Aggressive Mode SHOULD be implemented. In
addition, Quick Mode MUST be implemented as a mechanism to generate
fresh keying material and negotiate non-ISAKMP security services. In
addition, New Group Mode SHOULD be implemented as a mechanism to
define private groups for Diffie-Hellman exchanges. Implementations
MUST NOT switch exchange types in the middle of an exchange.
(omit)
=end html
=head1 SEE ALSO
perldoc V6evalTool
=begin html
IKE.html IKE Test Common Utility
=end html
=cut