<?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: LEAP and Session Key in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/leap-and-session-key/m-p/244040#M222434</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;LEAP is based on symetric keys which are generated on the RADIUS Server and the Client. The Client and Server do authentication using MS-CHAP which uses a U/P. The password is not sent over the network instead a hash key is sent. MSCHAP hashes are known to be volnurable to dictionary attacks. (If I remember correctly LEAP supports mutual auth but I forget how the client authenticates the server). If successfull both the client and the server generate the same WEP key based on the password and other clear text values. The server sends the key to the AP. This transfer is over a wired network but is encrypted. When LEAP is setup, a shared secret must be configured on the RADIUS server and the AP. This secret is used to encrypt the keys passed between the Server and AP. LEAP will also make sure that the WEP keys are rotated. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Serge&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 08 Mar 2004 20:34:03 GMT</pubDate>
    <dc:creator>s.vautour</dc:creator>
    <dc:date>2004-03-08T20:34:03Z</dc:date>
    <item>
      <title>LEAP and Session Key</title>
      <link>https://community.cisco.com/t5/wireless/leap-and-session-key/m-p/244039#M222433</link>
      <description>&lt;P&gt;With LEAP, a session key is used. Cisco docs point out, that after the authentication phase, the session key is distributed from the RADIUS Server to the AP and Client.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does this mean, that the session key is transmitted in cleartext?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would be very happy to have an answer or doc, which offers an answer to my question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;P&gt;Edgar&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 16:25:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/leap-and-session-key/m-p/244039#M222433</guid>
      <dc:creator>reinke</dc:creator>
      <dc:date>2021-07-04T16:25:47Z</dc:date>
    </item>
    <item>
      <title>Re: LEAP and Session Key</title>
      <link>https://community.cisco.com/t5/wireless/leap-and-session-key/m-p/244040#M222434</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;LEAP is based on symetric keys which are generated on the RADIUS Server and the Client. The Client and Server do authentication using MS-CHAP which uses a U/P. The password is not sent over the network instead a hash key is sent. MSCHAP hashes are known to be volnurable to dictionary attacks. (If I remember correctly LEAP supports mutual auth but I forget how the client authenticates the server). If successfull both the client and the server generate the same WEP key based on the password and other clear text values. The server sends the key to the AP. This transfer is over a wired network but is encrypted. When LEAP is setup, a shared secret must be configured on the RADIUS server and the AP. This secret is used to encrypt the keys passed between the Server and AP. LEAP will also make sure that the WEP keys are rotated. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Serge&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Mar 2004 20:34:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/leap-and-session-key/m-p/244040#M222434</guid>
      <dc:creator>s.vautour</dc:creator>
      <dc:date>2004-03-08T20:34:03Z</dc:date>
    </item>
  </channel>
</rss>

