<node id="620657">
  <nid>620657</nid>
  <type>event</type>
  <uid>
    <user id="27707"><![CDATA[27707]]></user>
  </uid>
  <created>1555680132</created>
  <changed>1555680132</changed>
  <title><![CDATA[PhD Proposal by Shan Chen]]></title>
  <body><![CDATA[<p><strong>Title:&nbsp;</strong>Towards Secure Communication and Authentication: Provable Security Analysis and New Constructions&nbsp;</p>

<p>&nbsp;</p>

<p>Shan Chen<br />
Ph.D. student in&nbsp;Computer&nbsp;Science<br />
School of&nbsp;Computer&nbsp;Science<br />
College of Computing<br />
Georgia Institute of Technology<br />
<br />
<strong>Date: </strong>Wednesday, April 24, 2019<br />
<strong>Time:</strong> 1:30 - 3:30 pm (EDT)<br />
<strong>Location:</strong> Klaus 3402<br />
<br />
<strong>Committee:</strong><br />
------------<br />
Dr. Alexandra Boldyreva (Advisor, School of&nbsp;Computer&nbsp;Science, Georgia Institute of Technology)<br />
Dr. Mustaque Ahamad (School of&nbsp;Computer&nbsp;Science, Georgia Institute of Technology)<br />
Dr. Vladimir Kolesnikov (School of&nbsp;Computer&nbsp;Science, Georgia Institute of Technology)<br />
<br />
<br />
<strong>Abstract:</strong><br />
-----------</p>

<p>Secure channel establishment protocols such as TLS are some of the most important cryptographic protocols, enabling the encryption of nearly half of all Internet traffic. Recently, there have been many formal security analyses for the most important low-latency protocols: the just-released TLS 1.3 and a relatively recent secure transport protocol QUIC from Google that is available in the Chrome browser. But their security, when layered with their underlying transport protocols, cannot be easily compared. The first work I will present in the proposal tries to solve this problem.</p>

<p>&nbsp;</p>

<p>After establishing a secure channel, a user often logs in to a server by typing in a password. But if the user&rsquo;s terminal has been fully compromised, the password will be leaked and his future communications cannot be protected. This problem is addressed by the second work I will present, which constructs the first user authentication and key exchange protocols that can tolerate strong corruptions on the client-side.</p>

<p>&nbsp;</p>

<p>The above protocol handled strong corruptions but still requires the user to type in some one-time password on the terminal, which is not very efficient. Recently, the Fast Identity Online (FIDO) Alliance has been working on a password-free user authentication standard called FIDO2. I will finally present our ongoing work on FIDO2 security analysis.</p>

<p>&nbsp;</p>
]]></body>
  <field_summary_sentence>
    <item>
      <value><![CDATA[Towards Secure Communication and Authentication: Provable Security Analysis and New Constructions ]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary>
  <field_time>
    <item>
      <value><![CDATA[2019-04-24T14:30:00-04:00]]></value>
      <value2><![CDATA[2019-04-24T16:30:00-04:00]]></value2>
      <rrule><![CDATA[]]></rrule>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_time>
  <field_fee>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_fee>
  <field_extras>
      </field_extras>
  <field_audience>
          <item>
        <value><![CDATA[Faculty/Staff]]></value>
      </item>
          <item>
        <value><![CDATA[Public]]></value>
      </item>
          <item>
        <value><![CDATA[Graduate students]]></value>
      </item>
          <item>
        <value><![CDATA[Undergraduate students]]></value>
      </item>
      </field_audience>
  <field_media>
      </field_media>
  <field_contact>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_contact>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_sidebar>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_sidebar>
  <field_phone>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_phone>
  <field_url>
    <item>
      <url><![CDATA[]]></url>
      <title><![CDATA[]]></title>
            <attributes><![CDATA[]]></attributes>
    </item>
  </field_url>
  <field_email>
    <item>
      <email><![CDATA[]]></email>
    </item>
  </field_email>
  <field_boilerplate>
    <item>
      <nid><![CDATA[]]></nid>
    </item>
  </field_boilerplate>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>221981</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[Graduate Studies]]></item>
      </og_groups_both>
  <field_categories>
          <item>
        <tid>1788</tid>
        <value><![CDATA[Other/Miscellaneous]]></value>
      </item>
      </field_categories>
  <field_keywords>
          <item>
        <tid>102851</tid>
        <value><![CDATA[Phd proposal]]></value>
      </item>
      </field_keywords>
  <field_userdata><![CDATA[]]></field_userdata>
</node>
