<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Questions regarding ISE Key Wrap functionality in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/questions-regarding-ise-key-wrap-functionality/m-p/4574749#M573562</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/218399"&gt;@coolsaurabh.hrc&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I haven't used key wrap feature. Just curious, why you're using it, and whether you have discovered a weakness in the existing MPPE key exchange?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It sounds like the Access-Accept is being returned to the NAS, and all is well? Perhaps the HMAC in the Access-Accept should not match that sent in the Access-Request. Have you tried analysing this in Wireshark?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 20 Mar 2022 21:39:38 GMT</pubDate>
    <dc:creator>Arne Bier</dc:creator>
    <dc:date>2022-03-20T21:39:38Z</dc:date>
    <item>
      <title>Questions regarding ISE Key Wrap functionality</title>
      <link>https://community.cisco.com/t5/network-access-control/questions-regarding-ise-key-wrap-functionality/m-p/4570573#M573471</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;Could someone please provide details on how&amp;nbsp;ISE calculates message-authentication-code AVP and insert into Access-accept packet when Key Wrap is enabled?&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;The problem we have is that the HMAC calculation on the&amp;nbsp;Access-accept received from ISE does not match with inserted 20 bytes of hmac sha1 value in AVP.&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;BR /&gt;Note: ISE sends access-accept, so ISE likes access-request packet (from us) and ISE’s hmac validation on access-request packet is correct.&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;Regards,&lt;/DIV&gt;&lt;DIV class=""&gt;Saurabh&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 15 Mar 2022 06:10:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/questions-regarding-ise-key-wrap-functionality/m-p/4570573#M573471</guid>
      <dc:creator>coolsaurabh.hrc</dc:creator>
      <dc:date>2022-03-15T06:10:31Z</dc:date>
    </item>
    <item>
      <title>Re: Questions regarding ISE Key Wrap functionality</title>
      <link>https://community.cisco.com/t5/network-access-control/questions-regarding-ise-key-wrap-functionality/m-p/4574749#M573562</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/218399"&gt;@coolsaurabh.hrc&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I haven't used key wrap feature. Just curious, why you're using it, and whether you have discovered a weakness in the existing MPPE key exchange?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It sounds like the Access-Accept is being returned to the NAS, and all is well? Perhaps the HMAC in the Access-Accept should not match that sent in the Access-Request. Have you tried analysing this in Wireshark?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 20 Mar 2022 21:39:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/questions-regarding-ise-key-wrap-functionality/m-p/4574749#M573562</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2022-03-20T21:39:38Z</dc:date>
    </item>
  </channel>
</rss>

