#!/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_3_5_1_P1_NP_0.seq,v 1.38.2.2 2005/11/22 10:05:47 ozoe Exp $ # $Id: R_RFC2408_3_5_1_P1_NP_0.seq,v 1.38.2.2 2005/11/22 10:05:47 ozoe Exp $ # ###################################################################### BEGIN { } END{ } 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); $ikeConfig{'isakmp_cookie_i'} = $cookie; #====== 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); %ret2 = ikePh1Send1st($IF0, 5, 0, 0, $cpp, \@ike, \%ikeConfig); if($ret2{'status'} == $IKE::FAIL) { ikeReset(); exit($V6evalTool::exitFail); } #------------------------------------------------------------------- vLogHTML("*** Phase-1 2nd message receive ***
"); #------------------------------------------------------------------- my @CHECK_FLAG = undef; $CHECK_FLAG[0] = shiftFlag(2); #Proposal payload my $OPTION_FLAG = $IKE_check::optionHash{'ProposalNumberCheck'}; my %ret = ikePh1Recv2nd($IF0, 5, 0, 0, $cpp, \@ike, \%ret2, \%ikeConfig,\@CHECK_FLAG,$OPTION_FLAG); if($ret{'status'} == $IKE::FAIL) { ikeReset(); exit($V6evalTool::exitFail); } #------------------------------------------------------------------- vLogHTML("Proposal Payload Format is correct
"); #------------------------------------------------------------------- #====================================================================== vLogHTML("*** Target test finish ***
"); #====================================================================== vStop($IF0); ikeReset(); ikeExitPass(); #NOTREACHED ###################################################################### __END__ =head1 NAME R_RFC2408_3_5_1_P1_NP_0 - [Responder Test]Proposal Payload format check =head1 TARGET End-Node =head1 SYNOPSIS =begin html 
  R_RFC2408_3_5_1_P1_NP_0.seq [-tooloption ...] -pkt R_RFC2408_3_5_1_P1_NP_0.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

      Proposal Payload Format
       
    • Next Payload field
      • 
       This field MUST only contain the value "2" or "0".
       Place the value of the Next Payload in the Next Payload field.
       (In Phase I, this field only contain the value "0"). 
       
    • RESERVED Fields
      • 
       All RESERVED fields in the ISAKMP protocol MUST be set to zero (0).
       Place the value zero (0) in the RESERVED field.
       
    • Payload Length field
      • 
       Place the length (in octets) of the payload in the Payload Length
       field.
       
    • Proposal Number field
      • 
       Identifies the Proposal number for the current payload.
       (In Phase I, this field contain the value "1".)
       
    • Protocol-ID field
      •  
       All implementations within the IPSEC DOI MUST support PROTO_ISAKMP.
       
    • SPI size field
      • 
       Length in octets of the SPI as defined by the Protocol-Id. 
       
    • Number of Transforms field
      • 
       Specifies the number of transforms for the Proposal.
       (In this test, this field contain the value "1".)
       
    • SPI field
      • 
       The sending entity's SPI.
       (In Phase I, this field is redundant and MAY be set to 0 or it MAY 
        contain the transmitting entity's cookie.)

  • 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
            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
                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.
=end html =head1 JUDGEMENT The first message must be accepted. And the second message's Proposal Payload Format must be base on description of RFC(see above Verification Points). =head1 TERMINATION Clean up SAD and SPD =head1 REFERENCE =begin html 
  RFC2407
  4.4.1.1 PROTO_ISAKMP


   The PROTO_ISAKMP type specifies message protection required during
   Phase I of the ISAKMP protocol.  The specific protection mechanism
   used for the IPSEC DOI is described in [IKE].  All implementations
   within the IPSEC DOI MUST support PROTO_ISAKMP.



  RFC2408


  2.5.2 RESERVED Fields


   The existence of RESERVED fields within ISAKMP payloads are used
   strictly to preserve byte alignment.  All RESERVED fields in the
   ISAKMP protocol MUST be set to zero (0) when a packet is issued.  The
   receiver SHOULD check the RESERVED fields for a zero (0) value and
   discard the packet if other values are found.


  (omit)


  3.5 Proposal Payload


  (omit)


                          1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     ! Next Payload  !   RESERVED    !         Payload Length        !
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     !  Proposal #   !  Protocol-Id  !    SPI Size   !# of Transforms!
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     !                        SPI (variable)                         !
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


  (omit)


    o  Next Payload (1 octet) - Identifier for the payload type of the
       next payload in the message.  This field MUST only contain the
       value "2" or "0".  If there are additional Proposal payloads in
       the message, then this field will be 2.  If the current Proposal
       payload is the last within the security association proposal,
       then this field will be 0.


    o  RESERVED (1 octet) - Unused, set to 0.


    o  Payload Length (2 octets) - Length in octets of the entire
       Proposal payload, including generic payload header, the Proposal
       payload, and all Transform payloads associated with this
       proposal.  In the event there are multiple proposals with the
       same proposal number (see section 4.2), the Payload Length field
       only applies to the current Proposal payload and not to all
       Proposal payloads.


    o  Proposal # (1 octet) - Identifies the Proposal number for the
       current payload.  A description of the use of this field is found
       in section 4.2.


    o  Protocol-Id (1 octet) - Specifies the protocol identifier for the
       current negotiation.  Examples might include IPSEC ESP, IPSEC AH,
       OSPF, TLS, etc.


    o  SPI Size (1 octet) - Length in octets of the SPI as defined by
       the Protocol-Id.  In the case of ISAKMP, the Initiator and
       Responder cookie pair from the ISAKMP Header is the ISAKMP SPI,
       therefore, the SPI Size is irrelevant and MAY be from zero (0) to
       sixteen (16).  If the SPI Size is non-zero, the content of the
       SPI field MUST be ignored.  If the SPI Size is not a multiple of
       4 octets it will have some impact on the SPI field and the
       alignment of all payloads in the message.  The Domain of
       Interpretation (DOI) will dictate the SPI Size for other
       protocols.


    o  # of Transforms (1 octet) - Specifies the number of transforms
       for the Proposal.  Each of these is contained in a Transform
       payload.


    o  SPI (variable) - The sending entity's SPI. In the event the SPI
       Size is not a multiple of 4 octets, there is no padding applied
       to the payload, however, it can be applied at the end of the
       message.


  (omit)


  5.3 Generic Payload Header Processing


   When creating any of the ISAKMP Payloads described in sections 3.4
   through 3.15 a Generic Payload Header is placed at the beginning of
   these payloads.  When creating the Generic Payload Header, the
   transmitting entity (initiator or responder) MUST do the following:


   1.  Place the value of the Next Payload in the Next Payload field.
       These values are described in section 3.1.


   2.  Place the value zero (0) in the RESERVED field.


   3.  Place the length (in octets) of the payload in the Payload Length
       field.


   4.  Construct the payloads as defined in the remainder of this
       section.


  (omit)


  5.5 Proposal Payload Processing


   When creating a Proposal Payload, the transmitting entity (initiator
   or responder) MUST do the following:


   1.  Determine the Protocol for this proposal.


   2.  Determine the number of proposals to be offered for this protocol
       and the number of transforms for each proposal.  Transforms are
       described in section 3.6.


   3.  Generate a unique pseudo-random SPI.


   4.  Construct a Proposal payload.


  (omit)
=end html =head1 SEE ALSO perldoc V6evalTool =begin html 
  IKE.html IKE Test Common Utility
=end html =cut