<?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: Enabling LTO4 Hardware Encryption from OpenVMS ?? in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/enabling-lto4-hardware-encryption-from-openvms/m-p/4682673#M100243</link>
    <description>Hi,&lt;BR /&gt;  See here for the VMS program written to load keys into LTO4 drives:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1171171" target="_blank"&gt;http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1171171&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;We found it was easier, on the latest generation MSL libraries (MSL2024, MSL4048, etc) to just purchase the encryption kit option. This provides a usb fob that sticks on the back of the library and contains the keys. We then set the libary such that the drives are always in encrypted mode and then VMS doesn't have to care about managing it.&lt;BR /&gt;&lt;BR /&gt;It would be necessary to use that program on a standalone (non-library) LTO4 drive. Especially since the drives lose the key when they are powered off, I would re-load it before each backup just to be sure. We did testing on a standalone drive with that program and it worked well.&lt;BR /&gt;&lt;BR /&gt;- Dave</description>
    <pubDate>Fri, 03 Sep 2010 01:14:11 GMT</pubDate>
    <dc:creator>David R. Lennon</dc:creator>
    <dc:date>2010-09-03T01:14:11Z</dc:date>
    <item>
      <title>Enabling LTO4 Hardware Encryption from OpenVMS ??</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/enabling-lto4-hardware-encryption-from-openvms/m-p/4682671#M100241</link>
      <description>I guess the basic question is &lt;BR /&gt;&lt;BR /&gt;Is it possible to use LTO4 hardware encryption without using using the LTO4 key management software.   i.e. using some DCL command (or qualifier) to tell the LTO4 to use its hardware encryption (and a key supplied at runtime) on the data being backed up.???  &lt;BR /&gt;&lt;BR /&gt;Dave.</description>
      <pubDate>Thu, 02 Sep 2010 13:03:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/enabling-lto4-hardware-encryption-from-openvms/m-p/4682671#M100241</guid>
      <dc:creator>The Brit</dc:creator>
      <dc:date>2010-09-02T13:03:34Z</dc:date>
    </item>
    <item>
      <title>Re: Enabling LTO4 Hardware Encryption from OpenVMS ??</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/enabling-lto4-hardware-encryption-from-openvms/m-p/4682672#M100242</link>
      <description>It looks like Data Protector does this, however for OpenVMS there is only a client.&lt;BR /&gt;&lt;BR /&gt;   As far as passing keys is concerned, I see many referenced to SPin and SPout (Security Protocol IN and Security Protocol OUT).    SPout can be used to set a key on an LTO4 Tapedrive from what I understand.&lt;BR /&gt;&lt;BR /&gt;Is there an OpenVMS equivalent to this??&lt;BR /&gt;&lt;BR /&gt;If I choose to use the LTO4 Key Management Software, how do I interface with it from OpenVMS?? (or do I not need to??)&lt;BR /&gt;&lt;BR /&gt;How can I confirm that my backup tapes are encrypted ??&lt;BR /&gt;&lt;BR /&gt;Dave.&lt;BR /&gt;&lt;BR /&gt;(So many Q's, and not many A's)</description>
      <pubDate>Thu, 02 Sep 2010 14:32:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/enabling-lto4-hardware-encryption-from-openvms/m-p/4682672#M100242</guid>
      <dc:creator>The Brit</dc:creator>
      <dc:date>2010-09-02T14:32:08Z</dc:date>
    </item>
    <item>
      <title>Re: Enabling LTO4 Hardware Encryption from OpenVMS ??</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/enabling-lto4-hardware-encryption-from-openvms/m-p/4682673#M100243</link>
      <description>Hi,&lt;BR /&gt;  See here for the VMS program written to load keys into LTO4 drives:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1171171" target="_blank"&gt;http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1171171&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;We found it was easier, on the latest generation MSL libraries (MSL2024, MSL4048, etc) to just purchase the encryption kit option. This provides a usb fob that sticks on the back of the library and contains the keys. We then set the libary such that the drives are always in encrypted mode and then VMS doesn't have to care about managing it.&lt;BR /&gt;&lt;BR /&gt;It would be necessary to use that program on a standalone (non-library) LTO4 drive. Especially since the drives lose the key when they are powered off, I would re-load it before each backup just to be sure. We did testing on a standalone drive with that program and it worked well.&lt;BR /&gt;&lt;BR /&gt;- Dave</description>
      <pubDate>Fri, 03 Sep 2010 01:14:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/enabling-lto4-hardware-encryption-from-openvms/m-p/4682673#M100243</guid>
      <dc:creator>David R. Lennon</dc:creator>
      <dc:date>2010-09-03T01:14:11Z</dc:date>
    </item>
    <item>
      <title>Re: Enabling LTO4 Hardware Encryption from OpenVMS ??</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/enabling-lto4-hardware-encryption-from-openvms/m-p/4682674#M100244</link>
      <description>David,&lt;BR /&gt;&lt;BR /&gt;Does Tom's program work to set the same key on standalone drives as with the encryption kit?&lt;BR /&gt;&lt;BR /&gt;I'm thinking about requirements to read the tapes at another site (such as a DR site) that isn't using an MSL tape library.</description>
      <pubDate>Sun, 26 Sep 2010 23:04:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/enabling-lto4-hardware-encryption-from-openvms/m-p/4682674#M100244</guid>
      <dc:creator>Eric Dittman</dc:creator>
      <dc:date>2010-09-26T23:04:13Z</dc:date>
    </item>
    <item>
      <title>Re: Enabling LTO4 Hardware Encryption from OpenVMS ??</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/enabling-lto4-hardware-encryption-from-openvms/m-p/4682675#M100245</link>
      <description>&lt;BR /&gt;We never tested if the same encryption key that is on the library usb fob can be loaded from VMS into a "standalone" LTO4 drive, such that the same tape can be readable.&lt;BR /&gt;&lt;BR /&gt;I don't see why not, however - it's all just ones and zeros with computers, right?</description>
      <pubDate>Mon, 27 Sep 2010 13:50:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/enabling-lto4-hardware-encryption-from-openvms/m-p/4682675#M100245</guid>
      <dc:creator>David R. Lennon</dc:creator>
      <dc:date>2010-09-27T13:50:33Z</dc:date>
    </item>
    <item>
      <title>Re: Enabling LTO4 Hardware Encryption from OpenVMS ??</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/enabling-lto4-hardware-encryption-from-openvms/m-p/4682676#M100246</link>
      <description>The chances of remote access working without a full-path test and functional verification can be assumed to be somewhere between one and zero, and - without evidence to the contrary - zero is always assumed.&lt;BR /&gt;&lt;BR /&gt;Put another way, there's even less of a chance I'd trust encryption without a periodic full-path verify, given this is heaped atop a complete lack of trust for whether a non-encrypted recovery will work.&lt;BR /&gt;&lt;BR /&gt;Put another way, this is absolutely certain to fail.&lt;BR /&gt;&lt;BR /&gt;Until you can prove it works.</description>
      <pubDate>Mon, 27 Sep 2010 14:36:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/enabling-lto4-hardware-encryption-from-openvms/m-p/4682676#M100246</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2010-09-27T14:36:15Z</dc:date>
    </item>
  </channel>
</rss>

