<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Authorization on trifinite.org</title>
    <link>https://trifinite.org/tags/authorization/</link>
    <description>Recent content in Authorization on trifinite.org</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 25 Jul 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://trifinite.org/tags/authorization/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Tesla Authorization Extraction/Replay Attack</title>
      <link>https://trifinite.org/stuff/tempa_autorization_replay_attack/</link>
      <pubDate>Mon, 25 Jul 2022 00:00:00 +0000</pubDate>
      
      <guid>https://trifinite.org/stuff/tempa_autorization_replay_attack/</guid>
      <description>Note: This is related to Project TEMPA. Please follow this link for an overview!
The Tesla Authorization Replay attack is using a tool like temparary in order to extract VCSEC AuthorizationResponses from a whitelisted smartphone app. For AuthorizationRequests - that are mainly used for passive entry functions - the vehicle communicates a challenge token, that the smartphone app has to answer with an AuthorizationResponse which is embedded in a VCSEC SignedMessage object that has a SIGNATURE_TYPE_AES_GCM_TOKEN SignatureType.</description>
    </item>
    
  </channel>
</rss>
