<?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>question Re: KMS Key roll excess versions in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/KMS-Key-roll-excess-versions/m-p/317175#M227043</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The key version is stored in the metadata so that the client knows which version of the key to request from the KMS. By incrementing the key version, the old (and incorrect) key is not retrieved when decrypting a file encrypted with the new key. By incrementing the key and not reusing key numbers there is less risk of race conditions and makes it clear to the administrator that the key in use has been incremented.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope that helps,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Michael&lt;/P&gt;</description>
    <pubDate>Wed, 26 May 2021 18:33:40 GMT</pubDate>
    <dc:creator>mridley</dc:creator>
    <dc:date>2021-05-26T18:33:40Z</dc:date>
  </channel>
</rss>

