#!/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/ENODE/R_RFC2408_5_11_2_1_HASH.seq,v 1.37.2.2 2005/11/22 10:05:47 ozoe Exp $ # $Id: R_RFC2408_5_11_2_1_HASH.seq,v 1.37.2.2 2005/11/22 10:05:47 ozoe Exp $ # ###################################################################### BEGIN { } use V6evalTool; use IKE; use IKE_check; my $IF0 = Link0; #====== 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(host, $TEST_TYPE, $SUPPORT); #====== Test Configuration ====== %ikeConfig = ( 'app_type' => 'ICMP', 'isakmp_src' => "$IKE::IKEAddr{IKE_NUT_NET0_HOST1_ADDR}", 'isakmp_dst' => "$IKE::IKEAddr{IKE_TN_NET1_HOST2_ADDR}", 'isakmp_dport' => '500', 'isakmp_ex_mode' => 'main', 'isakmp_doi' => 'ipsec_doi', 'isakmp_situation' => 'identity_only', 'isakmp_key_id' => "$IKE::IKEAddr{IKE_TN_NET1_HOST2_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_NET0_HOST1_ADDR}", 'isakmp_dst_id_type' => 'address', 'isakmp_dst_id' => "$IKE::IKEAddr{IKE_TN_NET1_HOST2_ADDR}", 'isakmp_num_pro' => '1', 'isakmp_num_trans' => '1', 'ipsec_id_type' => 'address', 'ipsec_src' => "$IKE::IKEAddr{IKE_TN_NET1_HOST2_ADDR}", 'ipsec_dst' => "$IKE::IKEAddr{IKE_NUT_NET0_HOST1_ADDR}", 'ipsec_src_id' => "$IKE::IKEAddr{IKE_NUT_NET0_HOST1_ADDR}", 'ipsec_dst_id' => "$IKE::IKEAddr{IKE_TN_NET1_HOST2_ADDR}", 'ipsec_supper' => 'any', 'ipsec_dupper' => 'any', 'ipsec_direction' => 'in', 'ipsec_pfs_group' => 'off', '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' => 'Transport', 'ipsec_p1_t1_lt' => '8', 'ipsec_p1_t1_lt_unit' => 'hour', ); #====== set TN's cookie ======== my $cookie = GetMD5("$IKE::IKEAddr{IKE_TN_NET1_HOST2_ADDR}"."$ikeConfig{'isakmp_dport'}".time()); $cookie = substr($cookie, 0, 16); my $nonce = '00000000000000000000000000000000'; $ikeConfig{'isakmp_cookie_i'} = $cookie; $ikeConfig{'isakmp_nonce_i'} = $nonce; #====== set other date about this test ======== #====== set ISAKMP SA, IPSEC SPD #====== vLogHTML("*** Target IKE initialization phase ***
"); ikeInit(%ikeConfig); #====== set Address of NUT ====== vLogHTML("*** Target initialization phase ***
"); vCapture($IF0); ikeSetAddr($IF0); #====== set ISAKMP SA packet frame, parameter #====== my $cpp = undef; my @ike = (); #====================================================================== vLogHTML("*** Target testing phase ***
"); #====================================================================== #------------------------------------------------------------------- vLogHTML("*** Phase-1 1st message send ***
"); #------------------------------------------------------------------- vClear($IF0); my %ret1 = ikePh1Send1st($IF0, 5, 0, 0, $cpp, \@ike, \%ikeConfig); if($ret1{'status'} == $IKE::FAIL) { ikeReset(); exit($V6evalTool::exitFail); } #------------------------------------------------------------------- vLogHTML("*** Phase-1 2nd message receive ***
"); #------------------------------------------------------------------- my @CHECK_FLAG = undef; $CHECK_FLAG[0] = 0; my $OPTION_FLAG = $IKE_check::optionHash{'none'}; my %ret2 = ikePh1Recv2nd($IF0, 5, 0, 0, $cpp, \@ike, \%ret1, \%ikeConfig,\@CHECK_FLAG,$OPTION_FLAG); if($ret2{'status'} == $IKE::FAIL) { ikeReset(); exit($V6evalTool::exitFail); } #------------------------------------------------------------------- vLogHTML("*** Phase-1 3rd message send ***
"); #------------------------------------------------------------------- vClear($IF0); my %ret3 = ikePh1Send3rd($IF0, 5, 0, 0, $cpp, \@ike, \%ret2, \%ikeConfig); if($ret3{'status'} == $IKE::FAIL) { ikeReset(); exit($V6evalTool::exitFail); } my @ike = (); #------------------------------------------------------------------- vLogHTML("*** Phase-1 4th message receive ***
"); #------------------------------------------------------------------- @CHECK_FLAG = undef; $CHECK_FLAG[0] = 0; #none my $OPTION_FLAG = $IKE_check::optionHash{'none'}; my %ret4 = ikePh1Recv4th($IF0, 5, 0, 0, $cpp, \@ike, \%ret3, \%ikeConfig,\@CHECK_FLAG,$OPTION_FLAG); if($ret4{'status'} == $IKE::FAIL) { ikeReset(); exit($V6evalTool::exitFail); } my @ike = (); #------------------------------------------------------------------- vLogHTML("*** Phase-1 5th message send ***
"); #------------------------------------------------------------------- vClear($IF0); $cpp = " -DINVALID_PHASE1_SEND_5TH_HASH "; my %ret5 = ikePh1Send5th($IF0, 5, 0, 0, $cpp, \@ike, \%ret4, \%ikeConfig); if($ret5{'status'} == $IKE::FAIL) { ikeReset(); exit($V6evalTool::exitFail); } if($IKE::NOTIFY_CHECK eq undef){ my @ike = (); #------------------------------------------------------------------- vLogHTML("*** Phase-1 6th message receive ***
"); #------------------------------------------------------------------- @CHECK_FLAG = undef; $CHECK_FLAG[0] = shiftFlag(5) + shiftFlag(8); #ID payload $OPTION_FLAG = $IKE_check::optionHash{'none'}; my %ret = ikePh1Recv6th($IF0, 5, 0, 0, $cpp, \@ike, \%ret5, \%ikeConfig,\@CHECK_FLAG,$OPTION_FLAG); if($ret{'status'} == $IKE::PASS) { vLogHTML(''); vLogHTML("NG:Phase-1 6th message is returned.
"); vLogHTML(''); ikeReset(); exit($V6evalTool::exitFail); }else{ vLogHTML(''); vLogHTML("OK:Phase-1 6th message is not returned.
"); vLogHTML(''); } }else{ #------------------------------------------------------------------- vLogHTML("*** Phase-1 Notify recv ***
"); #------------------------------------------------------------------- my @notifyMessageID=($IKE::notify_messages{'INVALID-HASH-INFORMATION'}); my $encryptiontype= '1'; $cpp=$ikeConfig{'cpp_phase1_recv_4th'}; %pktdesc = ( %pktdesc, 'isakmp_phase1_recv_4th' => 'Recv 2nd message from HOST1(NUT)' ); @ike = ( @ike, 'isakmp_phase1_recv_4th' ); my %ret_notify = ikeRecvNotify($IF0, 5, 0, 1, $cpp, \@ike, \%ret5, \%ikeConfig,\@notifyMessageID,$encryptiontype); if($ret_notify{'status'} >= 2) { ikeReset(); exit($V6evalTool::exitFail); } } #------------------------------------------------------------------- vLogHTML("Check the Hash to confirm it is supported is correct
"); #------------------------------------------------------------------- #====================================================================== vLogHTML("*** Target test finish ***
"); #====================================================================== vStop($IF0); ikeReset(); ikeExitPass(); #NOTREACHED ###################################################################### __END__ =head1 NAME R_RFC2408_5_11_2_1_HASH - [Responder Test] Check the Hash to confirm it is supported =head1 TARGET End-Node =head1 SYNOPSIS =begin html 
  R_RFC2408_5_11_2_1_HASH.seq [-tooloption ...] -pkt R_RFC2408_5_11_2_1_HASH.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):initiator
          |3ffe:501:ffff:101::11
          |                     
Net-y   --+--------+------------------------ 3ffe:501:ffff:101::/64
                   |
                   |
                 ROUTER-1(TN)
                   |3ffe:501:ffff:100::11
                   |
Net-z   --+--------+------------------------ 3ffe:501:ffff:100::/64
          |
          |3ffe:501:ffff:100:XXXX
        NUT:responder
  
    
  XXXX: EUI64 address

  • Verification Points

           Determine if the Hash is supported.  If the Hash determination
       fails, the message is discarded and the following actions are
       taken:
    
       (a)  The event, INVALID HASH INFORMATION, MAY be logged in the
            appropriate system audit file.
    
       (b)  An Informational Exchange with a Notification payload
            containing the INVALID-HASH-INFORMATION message type MAY be
            sent to the transmitting entity.  This action is dictated by
            a system security policy.

  • Configuration

      •        
    • Hash Payload Format(HOST-2:Initiator)
      • 
          Hash Data field : not include this field (invalid)
       
    • 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
            Upper
          
      
          
      
            NUT           
            NUT addr           
            HOST-2 addr           
            Main  
            IKE-TEST                               
            3DES           
            SHA           
            pre-shared key           
            2           
            8 Hour           
            NUT addr              
            PROTO_IPSEC_ESP  
            ESP_3DES           
            Transport           
            HMAC-SHA 
            8 Hour           
            any           
          
         
          
         
            HOST-2
            HOST-2 addr
            NUT addr
            Main
            IKE-TEST      
            3DES
            SHA
            pre-shared key           
            2           
            8 Hour
            HOST-2 addr    
            PROTO_IPSEC_ESP 
            ESP_3DES 
            Transport
            HMAC-SHA
            8 Hour 
            any
          
      
                
          
      
          *Ex Mode = Exchange mode
          *IDx = identity payload(FQDN or user FQDN  can also be chosen as IDx)
          *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
          *NUT addr = NUT address
          *HOST-2 addr = HOST-2 address
=end html =head1 TEST PROCEDURE =begin html 
  This test check is following.


           IDENTITY PROTECTION EXCHANGE


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


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


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


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


(5)  HDR*; IDii; HASH_I ========>                        <----Hash Data field : not include this field (invalid)


(6-A)                 X <========     HDR*; IDir; HASH_R <-----Must not transmit
                                           or
(6-B)                   <========     HDR*; HASH(1); N/D
                                      (HDR; N/D)
                   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. 


   3. Send the third message from TN
      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. Receive the fourth message from NUT
      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. Send the fifth message from TN
      In the fifth (5) message, the initiator send identification 
      information and the results of the agreed upon authentication 
      function(hash function). 


   6. Receive the sixth message from NUT
      In the sixth message (6-B), the responder indicates either an ISAKMP
      Notify Payload or an ISAKMP delete Payload.
=end html =head1 JUDGEMENT The first to the fourth message must be exchanged correctly. The fifth message must not be accepted. And the sixth message(6-A) must not be returned (* or INVALID-HASH-INFORMATION message(6-B) is returned). *option : if you want to check the retruned Notify message. =head1 TERMINATION Clean up SAD and SPD =head1 REFERENCE =begin html 
  RFC2408
  5.11 Hash Payload Processing


(omit)


   When a Hash payload is received, the receiving entity (initiator or
   responder) MUST do the following:


   1.  Determine if the Hash is supported.  If the Hash determination
       fails, the message is discarded and the following actions are
       taken:


       (a)  The event, INVALID HASH INFORMATION, MAY be logged in the
            appropriate system audit file.


       (b)  An Informational Exchange with a Notification payload
            containing the INVALID-HASH-INFORMATION message type MAY be
            sent to the transmitting entity.  This action is dictated by
            a system security policy.


   2.  Perform the Hash function as outlined in the DOI and/or Key
       Exchange protocol documents.  If the Hash function fails, the
       message is discarded and the following actions are taken:


       (a)  The event, INVALID HASH VALUE, MAY be logged in the
            appropriate system audit file.


       (b)  An Informational Exchange with a Notification payload
            containing the AUTHENTICATION-FAILED message type MAY be
            sent to the transmitting entity.  This action is dictated by
            a system security policy.
=end html =head1 SEE ALSO perldoc V6evalTool =begin html 
  IKE.html IKE Test Common Utility
=end html =cut