<?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 Contact Tracing Cryptography Specification in Tech Talk</title>
    <link>https://community.isc2.org/t5/Tech-Talk/Contact-Tracing-Cryptography-Specification/m-p/35228#M2631</link>
    <description>&lt;P&gt;I &lt;IMG id="heart" class="emoticon emoticon-heart" src="https://community.isc2.org/i/smilies/16x16_heart.png" alt="Heart" title="Heart" /&gt; cryptography. Here is another great read. It's the joint &lt;A href="https://covid19-static.cdn-apple.com/applications/covid19/current/static/contact-tracing/pdf/ContactTracing-CryptographySpecification.pdf" target="_blank" rel="noopener"&gt;Google + Apple cryptography specification&lt;/A&gt; for Contact Tracing. Pity no one ponied up to put their name on it. There is a 24hr window of opportunity where people can be re-identified. Is that by design?&amp;nbsp;The Rolling Proximity Identifiers are "privacy-preserving" identifiers that are sent in Bluetooth Advertisements. What is the probability of "collisions" on a Rolling Proximity Identifier? Security researchers, where are you?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Upon a positive test of a user for COVID-19, their Diagnosis Keys and associated DayNumbers are uploaded to the Diagnosis Server. A Diagnosis Server is a server that aggregates the Diagnosis Keys&amp;nbsp;from the users who tested positive and distributes them to all the user clients who are using contact&amp;nbsp;tracing.&lt;/P&gt;</description>
    <pubDate>Mon, 09 Oct 2023 09:30:34 GMT</pubDate>
    <dc:creator>AppDefects</dc:creator>
    <dc:date>2023-10-09T09:30:34Z</dc:date>
    <item>
      <title>Contact Tracing Cryptography Specification</title>
      <link>https://community.isc2.org/t5/Tech-Talk/Contact-Tracing-Cryptography-Specification/m-p/35228#M2631</link>
      <description>&lt;P&gt;I &lt;IMG id="heart" class="emoticon emoticon-heart" src="https://community.isc2.org/i/smilies/16x16_heart.png" alt="Heart" title="Heart" /&gt; cryptography. Here is another great read. It's the joint &lt;A href="https://covid19-static.cdn-apple.com/applications/covid19/current/static/contact-tracing/pdf/ContactTracing-CryptographySpecification.pdf" target="_blank" rel="noopener"&gt;Google + Apple cryptography specification&lt;/A&gt; for Contact Tracing. Pity no one ponied up to put their name on it. There is a 24hr window of opportunity where people can be re-identified. Is that by design?&amp;nbsp;The Rolling Proximity Identifiers are "privacy-preserving" identifiers that are sent in Bluetooth Advertisements. What is the probability of "collisions" on a Rolling Proximity Identifier? Security researchers, where are you?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Upon a positive test of a user for COVID-19, their Diagnosis Keys and associated DayNumbers are uploaded to the Diagnosis Server. A Diagnosis Server is a server that aggregates the Diagnosis Keys&amp;nbsp;from the users who tested positive and distributes them to all the user clients who are using contact&amp;nbsp;tracing.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Oct 2023 09:30:34 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/Contact-Tracing-Cryptography-Specification/m-p/35228#M2631</guid>
      <dc:creator>AppDefects</dc:creator>
      <dc:date>2023-10-09T09:30:34Z</dc:date>
    </item>
  </channel>
</rss>

