<?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: Any known problems w. Code Read Protection for LPC1769 in LPC Microcontrollers</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/Any-known-problems-w-Code-Read-Protection-for-LPC1769/m-p/699462#M28167</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-size: 10.5pt;"&gt;It is really annoying that hackers spend so much time trying to compromise our embedded applications. &amp;nbsp;Similar to LPC, I found that STM32 family was recently hacked with a very similar method (&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-size: 10.5pt;"&gt;&lt;A href="https://www.aisec.fraunhofer.de/en/FirmwareProtection.html" style="color: purple; text-decoration: underline;"&gt;https://www.aisec.fraunhofer.de/en/FirmwareProtection.html&lt;/A&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-size: 10.5pt;"&gt;).&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-size: 10.5pt;"&gt;Not to mention there’s a university team in Cambridge who has shared their experiences hacking lots of MCUs online (&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-size: 10.5pt;"&gt;&lt;A href="http://www.cl.cam.ac.uk/~sps32/NCL_2011.pdf" style="color: purple; text-decoration: underline;"&gt;http://www.cl.cam.ac.uk/~sps32/NCL_2011.pdf&lt;/A&gt;)&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-size: 10.5pt;"&gt;.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-size: 10.5pt;"&gt;I understand there’s a big difference between general purpose&amp;nbsp;MCUs and tamper resistant MCUs for secure payments and transactions, but it’s still very frustrating.&amp;nbsp; As a developer, I seriously hope NXP and other manufacturers work to make their entry level micros more resistant to these hacking threats.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 05 Dec 2017 22:46:56 GMT</pubDate>
    <dc:creator>albertocapuzzo</dc:creator>
    <dc:date>2017-12-05T22:46:56Z</dc:date>
    <item>
      <title>Any known problems w. Code Read Protection for LPC1769</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Any-known-problems-w-Code-Read-Protection-for-LPC1769/m-p/699460#M28165</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here it demonstrated how code read protection (CRP) is bypassed on the "LPC family"&lt;BR /&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D98eqp4WmHoQ" rel="nofollow" target="_blank"&gt;https://www.youtube.com/watch?v=98eqp4WmHoQ&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are ISP implementations different between different family members?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am using LPC1769, are there any known CRP problems known for this device?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any way I can make the power analysis (etc.) more difficult?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 10 Sep 2017 10:30:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Any-known-problems-w-Code-Read-Protection-for-LPC1769/m-p/699460#M28165</guid>
      <dc:creator>stenlarsson</dc:creator>
      <dc:date>2017-09-10T10:30:45Z</dc:date>
    </item>
    <item>
      <title>Re: Any known problems w. Code Read Protection for LPC1769</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Any-known-problems-w-Code-Read-Protection-for-LPC1769/m-p/699461#M28166</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The&amp;nbsp;bypass method demonstrated in the video&amp;nbsp;is known for a very long time.&lt;/P&gt;&lt;P&gt;Still, I find the&amp;nbsp;simplicity of how it can be done and systematically repeated quite worrying.&lt;/P&gt;&lt;P&gt;The lack of response and action from NXP is nothing but disturbing too, to be honest!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Sep 2017 10:30:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Any-known-problems-w-Code-Read-Protection-for-LPC1769/m-p/699461#M28166</guid>
      <dc:creator>hparracho</dc:creator>
      <dc:date>2017-09-20T10:30:12Z</dc:date>
    </item>
    <item>
      <title>Re: Any known problems w. Code Read Protection for LPC1769</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Any-known-problems-w-Code-Read-Protection-for-LPC1769/m-p/699462#M28167</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-size: 10.5pt;"&gt;It is really annoying that hackers spend so much time trying to compromise our embedded applications. &amp;nbsp;Similar to LPC, I found that STM32 family was recently hacked with a very similar method (&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-size: 10.5pt;"&gt;&lt;A href="https://www.aisec.fraunhofer.de/en/FirmwareProtection.html" style="color: purple; text-decoration: underline;"&gt;https://www.aisec.fraunhofer.de/en/FirmwareProtection.html&lt;/A&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-size: 10.5pt;"&gt;).&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-size: 10.5pt;"&gt;Not to mention there’s a university team in Cambridge who has shared their experiences hacking lots of MCUs online (&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-size: 10.5pt;"&gt;&lt;A href="http://www.cl.cam.ac.uk/~sps32/NCL_2011.pdf" style="color: purple; text-decoration: underline;"&gt;http://www.cl.cam.ac.uk/~sps32/NCL_2011.pdf&lt;/A&gt;)&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-size: 10.5pt;"&gt;.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-size: 10.5pt;"&gt;I understand there’s a big difference between general purpose&amp;nbsp;MCUs and tamper resistant MCUs for secure payments and transactions, but it’s still very frustrating.&amp;nbsp; As a developer, I seriously hope NXP and other manufacturers work to make their entry level micros more resistant to these hacking threats.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Dec 2017 22:46:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Any-known-problems-w-Code-Read-Protection-for-LPC1769/m-p/699462#M28167</guid>
      <dc:creator>albertocapuzzo</dc:creator>
      <dc:date>2017-12-05T22:46:56Z</dc:date>
    </item>
    <item>
      <title>Re: Any known problems w. Code Read Protection for LPC1769</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Any-known-problems-w-Code-Read-Protection-for-LPC1769/m-p/699463#M28168</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Apologies for the late response.&lt;/P&gt;&lt;P&gt;The LPC team is working on newer microcontrollers that are more resistant to such attack.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Dec 2017 22:00:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Any-known-problems-w-Code-Read-Protection-for-LPC1769/m-p/699463#M28168</guid>
      <dc:creator>ckphua</dc:creator>
      <dc:date>2017-12-07T22:00:01Z</dc:date>
    </item>
  </channel>
</rss>

