<?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: Encryption and RMS files in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/encryption-and-rms-files/m-p/3797525#M34217</link>
    <description>Thanks for the information!</description>
    <pubDate>Thu, 08 Jun 2006 05:59:01 GMT</pubDate>
    <dc:creator>Bart Van Cauter</dc:creator>
    <dc:date>2006-06-08T05:59:01Z</dc:date>
    <item>
      <title>Encryption and RMS files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/encryption-and-rms-files/m-p/3797519#M34211</link>
      <description>We are using an Alpha-server with Open VMS 7.3 and we have the following problem.&lt;BR /&gt;&lt;BR /&gt;We store our information in RMS files and have to encrypt particular fields in those files.&lt;BR /&gt;&lt;BR /&gt;This gave rise to the following questions:&lt;BR /&gt;&lt;BR /&gt;1.Do you have (or know off) encryption/decryption modules on OpenVMS (SHA-1, Triple DES 128) ?&lt;BR /&gt;&lt;BR /&gt;2.If we are able to encrypt/decrypt a particular field, will the SORT on sequential files still work if being used on these encrypted fields ?&lt;BR /&gt;&lt;BR /&gt;3.What happens with indexed files where the key needs to be encrypted? If we want to use that key, can we than fist encrypt and then do a direct read with the encrypted value and still get the correct record back ?&lt;BR /&gt;</description>
      <pubDate>Wed, 31 May 2006 07:57:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/encryption-and-rms-files/m-p/3797519#M34211</guid>
      <dc:creator>Bart Van Cauter</dc:creator>
      <dc:date>2006-05-31T07:57:33Z</dc:date>
    </item>
    <item>
      <title>Re: Encryption and RMS files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/encryption-and-rms-files/m-p/3797520#M34212</link>
      <description>Was curious and found this&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/openvms/6477pro.pdf" target="_blank"&gt;http://h71000.www7.hp.com/openvms/6477pro.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Wed, 31 May 2006 09:05:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/encryption-and-rms-files/m-p/3797520#M34212</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2006-05-31T09:05:38Z</dc:date>
    </item>
    <item>
      <title>Re: Encryption and RMS files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/encryption-and-rms-files/m-p/3797521#M34213</link>
      <description>Start reading at 4.4&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Wed, 31 May 2006 09:09:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/encryption-and-rms-files/m-p/3797521#M34213</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2006-05-31T09:09:37Z</dc:date>
    </item>
    <item>
      <title>Re: Encryption and RMS files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/encryption-and-rms-files/m-p/3797522#M34214</link>
      <description>Thanks, will surely read it!&lt;BR /&gt;&lt;BR /&gt;I'm on holiday till 7/6 but when i'm back i'll dig in to it!</description>
      <pubDate>Wed, 31 May 2006 09:13:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/encryption-and-rms-files/m-p/3797522#M34214</guid>
      <dc:creator>Bart Van Cauter</dc:creator>
      <dc:date>2006-05-31T09:13:45Z</dc:date>
    </item>
    <item>
      <title>Re: Encryption and RMS files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/encryption-and-rms-files/m-p/3797523#M34215</link>
      <description>Pls. note that since  (I think) V8.2 the ENCRYPT no longer needs a license, but is bundled with VMS. But this (old) product only supports AES encryption. V8.3 of VMS shall contain a new version with actual encryption methods.&lt;BR /&gt;&lt;BR /&gt;regards Kalle</description>
      <pubDate>Wed, 31 May 2006 09:48:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/encryption-and-rms-files/m-p/3797523#M34215</guid>
      <dc:creator>Karl Rohwedder</dc:creator>
      <dc:date>2006-05-31T09:48:58Z</dc:date>
    </item>
    <item>
      <title>Re: Encryption and RMS files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/encryption-and-rms-files/m-p/3797524#M34216</link>
      <description>&amp;gt;&amp;gt; If we are able to encrypt/decrypt a particular field, will the SORT on sequential files still work if being used on these encrypted fields ?&lt;BR /&gt;&lt;BR /&gt;The native sort utility will NOT understand the underlying data sort order. It will sort the encrypted bytes, which will have a diffrent order. I don't think you can solve that with 'collating sequences.&lt;BR /&gt;&lt;BR /&gt;You could write your own tool to use calleable sort and provide a comparison routine which which decode and compare.&lt;BR /&gt;&lt;BR /&gt;Conceivably the sort tool would allow you to specify such compare function in a shareable library and use LIB$FIS to activate it, but best I can tell such feature does not exist.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt; 3.What happens with indexed files where the key needs to be encrypted? &lt;BR /&gt;&lt;BR /&gt;Similar. You will only be able to do a 'direct match'. generic key matched ("JOHN" to find "JOHNES") and 'NEXT' operations will be meaningless.&lt;BR /&gt;&lt;BR /&gt;If you go this route I would recommend to consider an artifial primary key in mostly increasing key order, like a record creation timestamp, as the primary storage tool. This will help  avoid bucket splitting going crazy to deal with random inserts.&lt;BR /&gt;&lt;BR /&gt;hth,&lt;BR /&gt;Hein.&lt;BR /&gt;</description>
      <pubDate>Wed, 31 May 2006 10:32:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/encryption-and-rms-files/m-p/3797524#M34216</guid>
      <dc:creator>Hein van den Heuvel</dc:creator>
      <dc:date>2006-05-31T10:32:54Z</dc:date>
    </item>
    <item>
      <title>Re: Encryption and RMS files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/encryption-and-rms-files/m-p/3797525#M34217</link>
      <description>Thanks for the information!</description>
      <pubDate>Thu, 08 Jun 2006 05:59:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/encryption-and-rms-files/m-p/3797525#M34217</guid>
      <dc:creator>Bart Van Cauter</dc:creator>
      <dc:date>2006-06-08T05:59:01Z</dc:date>
    </item>
    <item>
      <title>Re: Encryption and RMS files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/encryption-and-rms-files/m-p/3797526#M34218</link>
      <description>&lt;!--!*#--&gt;&amp;gt; Karl Rohwedder said:&lt;BR /&gt;&amp;gt; But this (old) product only supports AES&lt;BR /&gt;&amp;gt; encryption. V8.3 of VMS shall contain a&lt;BR /&gt;&amp;gt; new version with actual encryption methods.&lt;BR /&gt;&lt;BR /&gt;Correction: the old version only supports DES encryption.  The new version will support AES (the Advanced Encryption Standard).  DES is a deprecated FIPS PUB standard effective May 2007.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://csrc.nist.gov/cryptval/DESTranPlan.pdf" target="_blank"&gt;http://csrc.nist.gov/cryptval/DESTranPlan.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Just a bit of clarification,&lt;BR /&gt;Aaron</description>
      <pubDate>Mon, 12 Jun 2006 18:41:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/encryption-and-rms-files/m-p/3797526#M34218</guid>
      <dc:creator>Aaron Sakovich</dc:creator>
      <dc:date>2006-06-12T18:41:33Z</dc:date>
    </item>
  </channel>
</rss>

