#!/usr/bin/perl # # Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004, 2005 Yokogawa Electric Corporation. # All rights reserved. # # Redistribution and use of this software in source and binary # forms, with or without modification, are permitted provided that # the following conditions and disclaimer are agreed and accepted # by the user: # # 1. Redistributions of source code must retain the above copyright # notice, this list of conditions and the following disclaimer. # # 2. Redistributions in binary form must reproduce the above copyright # notice, this list of conditions and the following disclaimer in # the documentation and/or other materials provided with # the distribution. # # 3. Neither the names of the copyrighters, the name of the project # which is related to this software (hereinafter referred to as # "project") nor the names of the contributors may be used to # endorse or promote products derived from this software without # specific prior written permission. # # 4. No merchantable use may be permitted without prior written # notification to the copyrighters. # # 5. The copyrighters, the project and the contributors may prohibit # the use of this software at any time. # # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHTERS, THE PROJECT AND # CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING # BUT NOT LIMITED THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS # FOR A PARTICULAR PURPOSE, ARE DISCLAIMED. IN NO EVENT SHALL THE # COPYRIGHTERS, THE PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, # INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES # (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR # SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) # HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, # STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING # IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE # POSSIBILITY OF SUCH DAMAGE. # # $TAHI: ct/ike/SGW/SG_I_RFC2409_6_1_2.seq,v 1.25.2.3 2005/11/22 10:06:04 ozoe Exp $ # $Id: SG_I_RFC2409_6_1_2.seq,v 1.25.2.3 2005/11/22 10:06:04 ozoe Exp $ # ###################################################################### BEGIN { } use V6evalTool; use IKE; use IKE_check; my $IF0 = Link0; my $IF1 = Link1; #====== get sequence arguments ====== foreach (@ARGV) { /^test_type=(\S+)/ && do {$TEST_TYPE=$1; next; }; /^support=(\S+)/ && do {$SUPPORT=$1; next; }; /^app_type=(\S+)/ && do {$IKE::APP_TYPE=$1; next; }; /^test_phase=(\S+)/ && do {$IKE::TEST_PHASE=$1; next; }; ikeExitError("Unknown sequence option '$_'"); } #====== check NUT type ====== ikeCheckNUT(sgw, $TEST_TYPE, $SUPPORT); #====== Test Configuration ====== %ikeConfig = ( 'app_type' => 'ICMP', 'isakmp_src' => "$IKE::IKEAddr{IKE_NUT_NET2_SGW1_ADDR}", 'isakmp_dst' => "$IKE::IKEAddr{IKE_TN_NET3_SGW2_ADDR}", 'isakmp_dport' => '500', 'isakmp_ex_mode' => 'main', 'isakmp_doi' => 'ipsec_doi', 'isakmp_situation' => 'identity_only', 'isakmp_key_id' => "$IKE::IKEAddr{IKE_TN_NET3_SGW2_ADDR}", 'isakmp_key_value' => 'IKE-TEST', 'isakmp_enc_alg' => '3des', 'isakmp_hash_alg' => 'sha1', 'isakmp_auth_method' => 'pre_shared_key', 'isakmp_dh_group' => '2', 'isakmp_lt' => '28800', 'isakmp_lt_unit' => 'seconds', 'isakmp_src_id_type' => 'address', 'isakmp_src_id' => "$IKE::IKEAddr{IKE_NUT_NET2_SGW1_ADDR}", 'isakmp_dst_id_type' => 'address', 'isakmp_dst_id' => "$IKE::IKEAddr{IKE_TN_NET3_SGW2_ADDR}", 'isakmp_num_pro' => '1', 'isakmp_num_trans' => '1', 'ipsec_id_type' => 'address', 'ipsec_src' => "$IKE::IKEAddr{IKE_NET0_ADDR}", 'ipsec_dst' => "$IKE::IKEAddr{IKE_NET4_ADDR}", 'ipsec_src_id' => "$IKE::IKEAddr{IKE_NET0_ADDR}", 'ipsec_dst_id' => "$IKE::IKEAddr{IKE_NET4_ADDR}", 'ipsec_tsrc' => "$IKE::IKEAddr{IKE_NUT_NET2_SGW1_ADDR}", 'ipsec_tdst' => "$IKE::IKEAddr{IKE_TN_NET3_SGW2_ADDR}", 'ipsec_end_src' => "$IKE::IKEAddr{IKE_TN_NET0_HOST1_ADDR}", 'ipsec_end_dst' => "$IKE::IKEAddr{IKE_TN_NET4_HOST2_ADDR}", 'ipsec_supper' => 'any', 'ipsec_dupper' => 'any', 'ipsec_direction' => 'out', 'ipsec_pfs_group' => 'on', 'ipsec_dh_group' => '1', 'ipsec_p_num' => '1', 'ipsec_p1_proto' => 'PROTO_IPSEC_ESP', 'ipsec_p1_t_num' => '1', 'ipsec_p1_t1_enc_alg' => 'ESP_3DES', 'ipsec_p1_t1_auth_mtd' => 'HMAC_SHA', 'ipsec_p1_t1_mode' => 'Tunnel', 'ipsec_p1_t1_lt' => '8', 'ipsec_p1_t1_lt_unit' => 'hour', ); #====== set TN's cookie and nonce ======== my $cookie = GetMD5("$IKE::IKEAddr{IKE_TN_NET3_SGW2_ADDR}"."$ikeConfig{'isakmp_dport'}".time()); $cookie = substr($cookie, 0, 16); my $nonce = '00000000000000000000000000000000'; $ikeConfig{'isakmp_cookie_r'} = $cookie; $ikeConfig{'isakmp_nonce_r'} = $nonce; vLogHTML("CKY-R: $ikeConfig{'isakmp_cookie_r'}
") if $IKE::remote_debug; vLogHTML("Nr-b: $ikeConfig{'isakmp_nonce_r'}
") if $IKE::remote_debug; vLogHTML("pre_shared key: $ikeConfig{'isakmp_key_value'}
") if $IKE::remote_debug; #====== set ISAKMP SA, IPSEC SPD #====== vLogHTML("*** Target IKE initialization phase ***
"); ikeInit(%ikeConfig); #====== set Address of NUT ====== vLogHTML("*** Target initialization phase ***
"); vCapture($IF0); vCapture($IF1); ikeSetAddr($IF0,$IF1,$IKE::address_debug); #====== set ISAKMP SA packet frame, parameter #====== my $cpp = undef; my @ike = (); $IKE::pktdesc{'echo_request_send_net0host1_net4host2'} = 'Send Echo Request from Host-1(TN) to Host-2(TN) via SGW1(NUT)'; my $ret0 = packetSendOnly($IF1, 'echo_request_send_net0host1_net4host2'); if($ret0 == $IKE::FAIL) { ikeReset(); exit($V6evalTool::exitFail); } my %ret1 = ikePh2PreSeqI($IF0,$cpp, \@ike, \%ikeConfig); #====================================================================== vLogHTML("*** Target testing phase start ***
"); #====================================================================== #------------------------------------------------------------------- vLogHTML("*** Phase-2 1st message recv ***
"); #------------------------------------------------------------------- my @CHECK_FLAG = undef; $CHECK_FLAG[0] = 0; #none my $OPTION_FLAG = $IKE_check::optionHash{'none'}; my %ret2 = ikePh2Recv($IF0, 5, 0, 0, $cpp, \@ike, \%ret1, \%ikeConfig,\@CHECK_FLAG,$OPTION_FLAG); #does KEpayload exists my $base = 'Frame_Ether.Packet_IPv6.Upp_UDP.Udp_ISAKMP'; my $plunderplainKey = $base . '.ISAKMP_Encryption.Decrypted.PlainText'; my $plunderplain = $ret2{$plunderplainKey}; print("plunderplain=$plunderplain\n"); if($plunderplain =~ /Pld_ISAKMP_KE/){ if($IKE::payload_check_debug > 0){ vLogHTML(''); vLogHTML("**OK KE Payload exists
"); vLogHTML(''); } }else{ vLogHTML(''); vLogHTML("**NG KE Payload does not exists
"); vLogHTML(''); $ret2{'status'} = $IKE::FAIL; } #Attribute check #check DH group=1 in all attribute ##################### # DH Group check ###################### my $atttype = 3; my $attvalue = $ikeConfig{'ipsec_dh_group'}; my $attret = &IKE_check::SpecificAttributeCheckFromSeq(\%ret2,$atttype,$attvalue,1); if($attret < 0){ $ret2{'status'} = $IKE::FAIL } if($ret2{'status'} == $IKE::FAIL) { ikeReset(); exit($V6evalTool::exitFail); } #------------------------------------------------------------------- vLogHTML("PFS with DH1 is correct
"); #------------------------------------------------------------------- #====================================================================== vLogHTML("*** Target test finish ***
"); #====================================================================== vStop($IF0); vStop($IF1); ikeReset(); ikeExitPass(); #NOTREACHED ###################################################################### __END__ =head1 NAME SG_I_RFC2409_6_1_2 - [Initiator Test] enable PFS with DH1 =head1 TARGET SGW =head1 SYNOPSIS =begin html 
  SG_I_RFC2409_6_1_2.seq [-tooloption ...] -pkt SG_I_RFC2409_6_1_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
=end html =head1 INITIALIZATION =begin html
  • Network Topology
    •                                  HOST-2(TN)
                                   |3ffe:501:ffff:104::11
                                   |
Net-v   --+------------------------+-------- 3ffe:501:ffff:104::/64
          |
          |
         SGW-2(TN):responder
          |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):initiator
          |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

             
    • DH Group
      • 
       Oakley implementations MUST support a MODP group with the 
       following prime and generator. This group is assigned id 1 (one).
       
    • PFS
      • 
       For PFS to exist the key used to protect transmission of data MUST
       NOT be used to derive any additional keys,
       and if the key used to protect transmission of data was derived 
       from some other keying material, that material MUST NOT be used to
       derive any more keys.
       
    • KE payload
      • 
       An optional Key Exchange payload can be exchanged to allow for an 
       additional Diffie-Hellman exchange and exponentiation per Quick Mode.
       While use of the key exchange payload with Quick Mode is 
       optional it MUST be supported.

  • 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
            DH Group
            PH2 Lt
            IDci
            IDcr
            Upper
          
      
          
      
            SGW-1           
            SGW-1 addr           
            SGW-2 addr           
            Main  
            IKE-TEST                               
            3DES           
            SHA           
            pre-shared key           
            2           
            8 Hour            
            SGW-1 addr              
            PROTO_IPSEC_ESP   
            ESP_3DES             
            Tunnel           
            HMAC-SHA 
            1  
            8 Hour           
            Net-z addr          
            Net-v addr   
            any            
          
         
          
         
            SGW-2
            SGW-2 addr
            SGW-1 addr
            Main
            IKE-TEST      
            3DES
            SHA
            pre-shared key           
            2           
            8 Hour
            SGW-2 addr    
            PROTO_IPSEC_ESP
            ESP_3DES     
            Tunnel
            HMAC-SHA
            1  
            8 Hour 
            Net-z addr          
            Net-v addr   
            any
          
      
                
        
      
          *Ex Mode = Exchange mode(Aggresive mode can also be chosen as Ex Mode)
          *IDx = identity payload(FQDN or user FQDN  can also be chosen as IDx)
          *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

  • Pre-Sequence

    •        In order to start the negotiation of IKE, 
       TN(HOST-1) transmits Echo Request to TN(HOST-2).
=end html =head1 TEST PROCEDURE =begin html 
  This test check is following.


 * PHASE I


Either IDENTITY PROTECTION EXCHANGE or AGGRESSIVE EXCHANGE is performed as a pre sequence.



           IDENTITY PROTECTION EXCHANGE


 #   Initiator(NUT)     Direction      Responder(TN)
(1)  HDR; SA            ========>


(2)                     <========       HDR; SA


(3)  HDR; KE; NONCE     ========>


(4)                     <========     HDR; KE; NONCE


(5)  HDR*; IDii; HASH_I ========>


(6)                     <========     HDR*; IDir; HASH_R


   1. Receive the first message from NUT
      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. Send the second message from TN
      In the second message (2), the responder indicates the protection
      suite it has accepted with the Security Association, Proposal, and
      Transform payloads. 


   3. Receive the third message from NUT
      In the third (3) message, the initiator send keying material 
      used to arrive at a common shared secret and random information 
      which is used to guarantee liveness and protect against replay attacks.


   4. Send the fourth message from TN
      In the fourth (4) message, the responder send keying material 
      used to arrive at a common shared secret and random information 
      which is used to guarantee liveness and protect against replay attacks.


   5. Receive the fifth message from NUT
      In the fifth (5) message, the initiator send identification 
      information and the results of the agreed upon authentication 
      function(hash function). 


   6. Send the sixth message from TN
      In the sixth (6) message, the responder send identification 
      information and the results of the agreed upon authentication 
      function(hash function).



                        AGGRESSIVE EXCHANGE


 #     Initiator(NUT)   Direction      Responder(TN)      NOTE
(1)  HDR; SA; KE;      =>                        Begin ISAKMP-SA or
                                                 Proxy negotiation
     NONCE; IDii                                 and Key Exchange


(2)                    <=     HDR; SA; KE;
                              NONCE; IDir; AUTH
                                                 Initiator Identity
                                                 Verified by Responder
                                                 Key Generated
                                                 Basic SA agreed upon


(3)  HDR*; AUTH        =>
                                                 Responder Identity
                                                 Verified by Initiator
                                                 SA established


   1. Recieve the first message from NUT
      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).  There
      can be only one Proposal and one Transform offered (i.e.  no choices)
      in order for the aggressive exchange to work.  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.  Random information provided by both parties SHOULD
      be used by the authentication mechanism to provide shared proof of
      participation in the exchange.  Additionally, the initiator transmits
      identification information.


   2. Send the second message from TN
      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.
      Random information provided by both parties SHOULD be used by the
      authentication mechanism to provide shared proof of participation in
      the exchange.  Additionally, the responder transmits identification
      information.  All of this information is transmitted under the
      protection of the agreed upon authentication function.  Local
      security policy dictates the action of the responder if no proposed
      protection suite is accepted.  One possible action is the
      transmission of a Notify payload as part of an Informational
      Exchange.


   3. Recieve the third message from NUT
      In the third (3) message, the initiator transmits the results of the
      agreed upon authentication function.  This information is transmitted
      under the protection of the common shared secret.  Local security
      policy dictates the action if an error occurs during these messages.
      One possible action is the transmission of a Notify payload as part
      of an Informational Exchange.



  The test sequence is following.


 * PHASE II


                      QUICK MODE


 #   Initiator(NUT)     Direction      Responder(TN)
(1)  HDR*, HASH(1), SA, 
    Ni, KE, IDci, IDcr; ========>
                Judgement (Check *1)


   1. Receive the first message from NUT
      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.KE is keying material 
      used to arrive at a common shared secret. IDci and IDcr is
      identification information.
=end html =head1 JUDGEMENT In Phase I , messages must be exchanged correctly. In Phase II , the first message which has KE payload and DH1 as SA attribute must be received. And must conform to above Configuration. =head1 TERMINATION Clean up SAD and SPD =head1 REFERENCE =begin html 
  RFC2409 
  3.3 Perfect Forward Secrecy


   When used in the memo Perfect Forward Secrecy (PFS) refers to the
   notion that compromise of a single key will permit access to only
   data protected by a single key. For PFS to exist the key used to
   protect transmission of data MUST NOT be used to derive any
   additional keys, and if the key used to protect transmission of data
   was derived from some other keying material, that material MUST NOT
   be used to derive any more keys.


   Perfect Forward Secrecy for both keys and identities is provided in
   this protocol. (Sections 5.5 and 8).


  (omit)


  5.5 Phase 2 - Quick Mode


  (omit)


   Quick Mode is essentially a SA negotiation and an exchange of nonces
   that provides replay protection. The nonces are used to generate
   fresh key material and prevent replay attacks from generating bogus
   security associations.  An optional Key Exchange payload can be
   exchanged to allow for an additional Diffie-Hellman exchange and
   exponentiation per Quick Mode. While use of the key exchange payload
   with Quick Mode is optional it MUST be supported.


  (omit)


  6.1 First Oakley Default Group


   Oakley implementations MUST support a MODP group with the following
   prime and generator. This group is assigned id 1 (one).


      The prime is: 2^768 - 2 ^704 - 1 + 2^64 * { [2^638 pi] + 149686 }
      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 A63A3620 FFFFFFFF FFFFFFFF


      The generator is: 2.
=end html =head1 SEE ALSO perldoc V6evalTool =begin html 
  IKE.html IKE Test Common Utility
=end html =cut