#!/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_RFC2408_5_10_1_1_CR.seq,v 1.18.2.3 2005/11/22 10:06:02 ozoe Exp $ # $Id: SG_I_RFC2408_5_10_1_1_CR.seq,v 1.18.2.3 2005/11/22 10:06:02 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' => 'rsasig', 'isakmp_dh_group' => '2', 'isakmp_certificate_type' => 'x509', 'isakmp_certificate_file' => 'NUTcert.pem', 'isakmp_privkey_file' => 'NUTprivkey.pem', 'isakmp_lt' => '28800', 'isakmp_lt_unit' => 'seconds', 'isakmp_src_id_type' => 'asn1dn', # 'isakmp_src_id' => "root\@nut.com", 'isakmp_dst_id_type' => 'asn1dn', # 'isakmp_dst_id' => "root\@tn.com", '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' => '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' => '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 = (); #====================================================================== vLogHTML("*** Target testing phase ***
"); #------------------------------------------------------------------- vLogHTML("*** Phase-1 1st message recv ***
"); #------------------------------------------------------------------- $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 @CHECK_FLAG = undef; $CHECK_FLAG[0] = 0; #none my $OPTION_FLAG = $IKE_check::optionHash{'Phase1HashCheck'}; my %ret1 = ikePh1Recv('Link0', 10, 0, 0, $cpp, \@ike, \%ikeConfig,\@CHECK_FLAG,$OPTION_FLAG); if($ret1{'status'} == $IKE::FAIL) { ikeReset(); exit($V6evalTool::exitFail); } #------------------------------------------------------------------- vLogHTML("*** Phase-1 2nd message send ***
"); #------------------------------------------------------------------- vClear($IF0); vClear($IF1); my %ret2 = ikePh1Send2nd($IF0, 5, 0, 0, $cpp, \@ike, \%ret1, \%ikeConfig); if($ret2{'status'} == $IKE::FAIL) { ikeReset(); exit($V6evalTool::exitFail); } #------------------------------------------------------------------- vLogHTML("*** Phase-1 3rd message recv ***
"); #------------------------------------------------------------------- @CHECK_FLAG = undef; $CHECK_FLAG[0] = 0; #none $OPTION_FLAG = $IKE_check::optionHash{'none'}; my %ret3 = ikePh1Recv3rd($IF0, 5, 0, 0, $cpp, \@ike, \%ret2, \%ikeConfig,\@CHECK_FLAG,$OPTION_FLAG); if($ret3{'status'} == $IKE::FAIL) { ikeReset(); exit($V6evalTool::exitFail); } my @ike = (); #------------------------------------------------------------------- vLogHTML("*** Phase-1 4th message send ***
"); #------------------------------------------------------------------- vClear($IF0); vClear($IF1); $cpp = ' -DVALID_PHASE1_SEND_4th_CR '; my %ret4 = ikePh1Send4th($IF0, 5, 0, 0, $cpp, \@ike, \%ret3, \%ikeConfig); if($ret4{'status'} == $IKE::FAIL) { ikeReset(); exit($V6evalTool::exitFail); } #------------------------------------------------------------------- vLogHTML("*** Phase-1 5th message recv ***
"); #------------------------------------------------------------------- @CHECK_FLAG = undef; $CHECK_FLAG[0] = shiftFlag(7); #CR payload $OPTION_FLAG = $IKE_check::optionHash{'none'}; my %ret5 = ikePh1Recv5th($IF0, 5, 0, 0, $cpp, \@ike,\%ret4, \%ikeConfig,\@CHECK_FLAG,$OPTION_FLAG); if($ret{'status'} == $IKE::FAIL) { ikeReset(); exit($V6evalTool::exitFail); } #------------------------------------------------------------------- vLogHTML(" Certificate Request Payload Format is correct
"); #------------------------------------------------------------------- #====================================================================== vLogHTML("*** Target test finish ***
"); #====================================================================== vStop($IF0); vStop($IF1); ikeReset(); ikeExitPass(); #NOTREACHED ###################################################################### __END__ =head1 NAME SG_I_RFC2408_5_10_1_1_CR - [Initiator Test] Certificate Request Payload Format check =head1 TARGET SGW =head1 SYNOPSIS =begin html 
  SG_I_RFC2408_5_10_1_1_CR.seq [-tooloption ...] -pkt SG_I_RFC2408_5_10_1_1_CR.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 

      Certificate Request Payload Format
      
       
    • Next Payload field
      • 
       Place the value of the Next Payload in the Next Payload field.
       
    • 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.
       
    • Certificate Type field
      • 
       Contains an encoding of the type of certificate requested
       
    • Certificate Authority field
      • 
       Contains an encoding of an acceptable certificate authority for 
       the type of certificate requested.

  • Configuration

      •        
    • Initiator and Responder generate the public key and the secret key
      • 
       
    • 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           
            Main  
                                           
            3DES           
            SHA           
            RSA signatures           
            2           
            8 Hour            
            SGW-1 addr              
            PROTO_IPSEC_ESP   
            ESP_3DES             
            Tunnel           
            HMAC-SHA  
            8 Hour           
            Net-z addr          
            Net-v addr   
            any            
          
         
          
         
            SGW-2
            SGW-2 addr
            SGW-1 addr
            Main
                  
            3DES
            SHA
            RSA signatures           
            2           
            8 Hour
            SGW-2 addr    
            PROTO_IPSEC_ESP
            ESP_3DES     
            Tunnel
            HMAC-SHA 
            8 Hour 
            Net-z addr          
            Net-v addr   
            any
          
      
                
        
      
          *Ex Mode = Exchange 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.


           IDENTITY PROTECTION EXCHANGE


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


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


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


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


(5)  HDR*; IDii; CERT;
       CERT Req; SIG_I  ========>
                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).


   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.
      Additionally the responder send Certificate Request Payload.


   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. The signed data, SIG_I is the result of the negotiated 
      digital signature algorithm applied to HASH_I.
      Additionally the initiator send Certificate and Certificate
      Request Payload
=end html =head1 JUDGEMENT The first to the fourth message must be exchanged correctly. The fifth message's Certificate Request Payload Format must be base on description of RFC(see above Verification Points). And must conform to above Configuration. =head1 TERMINATION Clean up SAD and SPD =head1 REFERENCE =begin html 
  RFC2408
  3.10 Certificate Request 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        !
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     !  Cert. Type   !                                               !
     +-+-+-+-+-+-+-+-+                                               !
     ~                    Certificate Authority                      ~
     !                                                               !
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


  (omit)


    o  Next Payload (1 octet) - Identifier for the payload type of the
       next payload in the message.  If the current payload is the last
       in the message, then this field will be 0.


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


    o  Payload Length (2 octets) - Length in octets of the current
       payload, including the generic payload header.


    o  Certificate Type (1 octet) - Contains an encoding of the type of
       certificate requested.  Acceptable values are listed in section
       3.9.


    o  Certificate Authority (variable length) - Contains an encoding of
       an acceptable certificate authority for the type of certificate
       requested.  As an example, for an X.509 certificate this field
       would contain the Distinguished Name encoding of the Issuer Name
       of an X.509 certificate authority acceptable to the sender of
       this payload.  This would be included to assist the responder in
       determining how much of the certificate chain would need to be
       sent in response to this request.  If there is no specific
       certificate authority requested, this field SHOULD not be
       included.


  (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.10 Certificate Request Payload Processing


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


   1.  Determine the type of Certificate Encoding to be requested.  This
       may be specified by the DOI.


   2.  Determine the name of an acceptable Certificate Authority which
       is to be requested (if applicable).


   3.  Construct a Certificate Request payload.


   4.  Transmit the message to the receiving entity as described in
       section 5.1.


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