<?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 Prevent copying files in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/prevent-copying-files/m-p/4989683#M29703</link>
    <description>Consider files being readable from anywhere (locally (TYPE, EDIT) or remotely (in case of NFS mounted disks, or accesable by Samba or Advanced server). However, I would like these files be unmodifyable by any of these access methods unless privileged. Even more, I would like to be these files non-copyable as well. That implies: not accessable for copying it to any other location, including printers, other disks and locations (inclusing FTP and similar), and not even copying it via an editor (load file, save it under a different name (and location). &lt;BR /&gt;Is there a (VMS-native) way to be able to do so?</description>
    <pubDate>Mon, 10 Jul 2006 06:18:13 GMT</pubDate>
    <dc:creator>Willem Grooters</dc:creator>
    <dc:date>2006-07-10T06:18:13Z</dc:date>
    <item>
      <title>Prevent copying files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/prevent-copying-files/m-p/4989683#M29703</link>
      <description>Consider files being readable from anywhere (locally (TYPE, EDIT) or remotely (in case of NFS mounted disks, or accesable by Samba or Advanced server). However, I would like these files be unmodifyable by any of these access methods unless privileged. Even more, I would like to be these files non-copyable as well. That implies: not accessable for copying it to any other location, including printers, other disks and locations (inclusing FTP and similar), and not even copying it via an editor (load file, save it under a different name (and location). &lt;BR /&gt;Is there a (VMS-native) way to be able to do so?</description>
      <pubDate>Mon, 10 Jul 2006 06:18:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/prevent-copying-files/m-p/4989683#M29703</guid>
      <dc:creator>Willem Grooters</dc:creator>
      <dc:date>2006-07-10T06:18:13Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent copying files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/prevent-copying-files/m-p/4989684#M29704</link>
      <description>I think, that if the files are readable, it would be impossible to prevent users from copying them to a local location.&lt;BR /&gt;To prevent modifications should be possible with file protection.&lt;BR /&gt;&lt;BR /&gt;regards Kalle</description>
      <pubDate>Mon, 10 Jul 2006 06:26:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/prevent-copying-files/m-p/4989684#M29704</guid>
      <dc:creator>Karl Rohwedder</dc:creator>
      <dc:date>2006-07-10T06:26:11Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent copying files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/prevent-copying-files/m-p/4989685#M29705</link>
      <description>Willem,&lt;BR /&gt;&lt;BR /&gt;You can prevent access to files with protected subsystems.&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/doc/732FINAL/aa-q2hlg-te/aa-q2hlg-te.HTMl" target="_blank"&gt;http://h71000.www7.hp.com/doc/732FINAL/aa-q2hlg-te/aa-q2hlg-te.HTMl&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;As I read it, you can prevent COPY, FTP and others to read the file while allowing TYPE and EDIT. However, this is only usable if you restrict all but real file viewers (not able to do save as).&lt;BR /&gt;&lt;BR /&gt;May be better to prevent all access except when done with a real file viewer (you can write yourself).&lt;BR /&gt;&lt;BR /&gt;Never used it, but hey, I work in a bank.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Mon, 10 Jul 2006 07:13:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/prevent-copying-files/m-p/4989685#M29705</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2006-07-10T07:13:54Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent copying files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/prevent-copying-files/m-p/4989686#M29706</link>
      <description>I think if you can read with TYPE then the output of TYPE could be redirected therefore copying the file. Also what about terminal emulators - if they display a file then it is potentially saved in the terminal emulator session history file and therefore a copy exists. &lt;BR /&gt;&lt;BR /&gt;Why do you want to prevent the copy - Security, as always, is a people problem.&lt;BR /&gt;</description>
      <pubDate>Mon, 10 Jul 2006 07:53:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/prevent-copying-files/m-p/4989686#M29706</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2006-07-10T07:53:29Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent copying files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/prevent-copying-files/m-p/4989687#M29707</link>
      <description>Willem,&lt;BR /&gt;&lt;BR /&gt;Protected subsystems would work with regards to the access from the OoenVMS side.&lt;BR /&gt;&lt;BR /&gt;Unfortunately, it is nearly impossible to control the other side of the connection. Screen scraping of data from the client side is virtually unknowable. This has figured in some discussions about data privacy following incidents such as the one involving the US Veterans Administration.&lt;BR /&gt;&lt;BR /&gt;Security measures must always be considered with the knowledge that the precautions and preventitive measures have limitations, and an awareness of what those limitations are.&lt;BR /&gt;&lt;BR /&gt;- Bob Gezelter, &lt;A href="http://www.rlgsc.com" target="_blank"&gt;http://www.rlgsc.com&lt;/A&gt;</description>
      <pubDate>Mon, 10 Jul 2006 08:13:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/prevent-copying-files/m-p/4989687#M29707</guid>
      <dc:creator>Robert Gezelter</dc:creator>
      <dc:date>2006-07-10T08:13:09Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent copying files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/prevent-copying-files/m-p/4989688#M29708</link>
      <description>Willem,&lt;BR /&gt;&lt;BR /&gt;You might be able to do this with a protected subsystem controlling access to the source data, but only presenting it to clients transformed into some kind of graphical format, presented via a web server as HTML with caching and right click disabled. You may also need to to introduce some noise to inhibit screen capture and OCR. However, it would NOT necessarily inhibit printing the graphical result.&lt;BR /&gt;&lt;BR /&gt;Of course, no matter what you do, you can't prevent someone from simply transcribing, or even photographing the data off the screen.</description>
      <pubDate>Mon, 10 Jul 2006 20:56:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/prevent-copying-files/m-p/4989688#M29708</guid>
      <dc:creator>John Gillings</dc:creator>
      <dc:date>2006-07-10T20:56:35Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent copying files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/prevent-copying-files/m-p/4989689#M29709</link>
      <description>I know it doesn't exist, but it would be a nice feature. IIRC, CDD had (has?) mentioned the ability to specify COPY as a allowed fnction in an ACL and it would be cool to have something like that in the base OS.</description>
      <pubDate>Sun, 08 Oct 2006 15:28:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/prevent-copying-files/m-p/4989689#M29709</guid>
      <dc:creator>Willem Grooters</dc:creator>
      <dc:date>2006-10-08T15:28:42Z</dc:date>
    </item>
  </channel>
</rss>

