Documentation:Unix Section 4 - Revision history

Clipka: canonicalize a version number

2021-06-09T15:39:09Z

canonicalize a version number

Jholsenback: generic version

2017-07-04T11:30:40Z

generic version

Clipka: /* Permitted Paths */ version number in file paths

2017-07-01T08:57:25Z

Permitted Paths: version number in file paths

Clipka: /* Configuration file format */ version number in file path

2017-07-01T08:56:05Z

Configuration file format: version number in file path

Jholsenback: 1 revision: link repair

2012-07-23T19:27:37Z

1 revision: link repair

Jholsenback: link repair

2012-07-21T20:55:59Z

link repair

Jholsenback: itc

2011-12-07T05:26:53Z

itc

Jholsenback: cleanup

2010-12-13T15:08:17Z

cleanup

Show changes

Jholsenback: cleanup

2010-12-13T13:50:21Z

cleanup

Jholsenback: ux cleanup pass

2010-10-20T09:47:16Z

ux cleanup pass

@@ Line 10: / Line 10: @@
 {{#indexentry:unix, I/O Restrictions}}
-<p>I/O Restrictions is a feature that was introduced in POV-Ray for Unix 3.5. The purpose of this feature is to attempt to at least partially protect a machine running POV-Ray from having files read or written outside of a given set of directories.</p>
+<p>I/O Restrictions is a feature that was introduced in POV-Ray for Unix v3.5. The purpose of this feature is to attempt to at least partially protect a machine running POV-Ray from having files read or written outside of a given set of directories.</p>
 <p>The need for this is related to the fact that the POV-Ray scene language has, over the years, become something more akin to a scripting language combined with a scene-description model. It is now possible to write obfuscated POV-Ray code, and to open, create, read and write arbitrary files anywhere on the target system's hard disk, subject to operating system permission.</p>

@@ Line 26: / Line 26: @@
 <p>The I/O Restrictions are configured by two separate configuration files. This can be a system-wide configuration, or a user configuration file located in the following places, on most systems <code>$PREFIX</code> is <code>/usr/local</code>.</p>
 <ul>
-   <li><code>$PREFIX/etc/povray/3.8/povray.conf</code></li>
+   <li><code>$PREFIX/etc/povray/vX.y/povray.conf</code></li>
-   <li><code>$HOME/.povray/3.8/povray.conf</code></li>
+   <li><code>$HOME/.povray/vX.y/povray.conf</code></li>
 </ul>
@@ Line 76: / Line 76: @@
 <p>If the directory name contains spaces it has to be quoted or doubly-quoted. There can be spaces before and after the equal sign. Read-only and read/write entries can be specified in any order.</p>
-<p>If you want the permissions for a specified directory to also extend to all of its subdirectories wildcards are permitted.</p>
+<p>If you want the permissions for a specified directory to also extend to all of its sub-directories wildcards are permitted.</p>
 <p>For example:</p>
@@ Line 84: / Line 84: @@
 </pre>
-<p>Both relative and absolute paths are permitted, so <em>the dot</em> character can be especially useful.  The install directory, typically <code>/usr/local/share/povray-3.8</code> or <code>/usr/share/povray-3.8</code>, can be specified with <code>%INSTALLDIR%</code>, the user home directory with <code>%HOME%</code>.  The install directory and its
+<p>Both relative and absolute paths are permitted, so <em>the dot</em> character can be especially useful. The install directory, typically <code>/usr/local/share/povray/vX.y</code> or <code>/usr/share/povray/vX.y</code> can be specified with <code>%INSTALLDIR%</code> and the user home directory with <code>%HOME%</code>. The install directory and its descendants are typically only writable by root; therefore it does not make sense to have <code>%INSTALLDIR%</code> in read/write directory paths.</p>
-<p class="Note"><strong>Note:</strong> Since user-level permissions are at least as strict as system-level restrictions, any paths specified in the system-wide <code>povray.conf</code> will also need to be specified in <code>~/.povray/3.8/povray.conf</code> if this file exists.</p>
+<p class="Note"><strong>Note:</strong> Since user-level permissions are at least as strict as system-level restrictions, any paths specified in the system-wide <code>povray.conf</code> will also need to be specified in <code>~/.povray/vX.y/povray.conf</code> if this file exists.</p>
 ====Examples for path settings====

@@ Line 84: / Line 84: @@
 </pre>
-<p>Both relative and absolute paths are permitted, so <em>the dot</em> character can be especially useful.  The install directory, typically <code>/usr/local/share/povray-3.7</code> or <code>/usr/share/povray-3.7</code>, can be specified with <code>%INSTALLDIR%</code>, the user home directory with <code>%HOME%</code>.  The install directory and its
+<p>Both relative and absolute paths are permitted, so <em>the dot</em> character can be especially useful.  The install directory, typically <code>/usr/local/share/povray-3.8</code> or <code>/usr/share/povray-3.8</code>, can be specified with <code>%INSTALLDIR%</code>, the user home directory with <code>%HOME%</code>.  The install directory and its
 descendents are typically only writable by root; therefore it does not make sense to have <code>%INSTALLDIR%</code> in read/write directory paths.</p>
-<p class="Note"><strong>Note:</strong> Since user-level permissions are at least as strict as system-level restrictions, any paths specified in the system-wide <code>povray.conf</code> will also need to be specified in <code>~/.povray/3.7/povray.conf</code> if this file exists.</p>
+<p class="Note"><strong>Note:</strong> Since user-level permissions are at least as strict as system-level restrictions, any paths specified in the system-wide <code>povray.conf</code> will also need to be specified in <code>~/.povray/3.8/povray.conf</code> if this file exists.</p>
 ====Examples for path settings====

@@ Line 26: / Line 26: @@
 <p>The I/O Restrictions are configured by two separate configuration files. This can be a system-wide configuration, or a user configuration file located in the following places, on most systems <code>$PREFIX</code> is <code>/usr/local</code>.</p>
 <ul>
-   <li><code>$PREFIX/etc/povray/3.7/povray.conf</code></li>
+   <li><code>$PREFIX/etc/povray/3.8/povray.conf</code></li>
-   <li><code>$HOME/.povray/3.7/povray.conf</code></li>
+   <li><code>$HOME/.povray/3.8/povray.conf</code></li>
 </ul>

@@ Line 62: / Line 62: @@
 </ul>
-<p>See the section <!--<linkto "Setting POV-Ray Options">POV-Ray Options</linkto>--->[[Documentation:Reference Section 1.2#Shell-out to Operating System|Shell-out to Operating System]] for more details.</p>
+<p>See the section <!--<linkto "Setting POV-Ray Options">POV-Ray Options</linkto>--->[[Reference:Shell Command Options|Shell-out to Operating System]] for more details.</p>
 ===Permitted Paths===

← Older revision	Revision as of 19:27, 23 July 2012
(No difference)

@@ Line 8: / Line 8: @@
 <!--</wikitalk>--->
 ==I/O Restrictions==
-<!--<indexentry "I/O Restrictions">--->
+{{#indexentry:unix, I/O Restrictions}}
 <p>I/O Restrictions is a feature that was introduced in POV-Ray for Unix 3.5. The purpose of this feature is to attempt to at least partially protect a machine running POV-Ray from having files read or written outside of a given set of directories.</p>

@@ Line 47: / Line 47: @@
 <p>
 The I/O Restrictions are configured by a separate configuration file.  This can be a
-system-wide configuration file (<code>PREFIX/etc/povray/3.6/povray.conf</code>,
+system-wide configuration file (<code>PREFIX/etc/povray/3.7/povray.conf</code>,
 <code>PREFIX</code> by default is <code>/usr/local</code>) or a user configuration file
-(<code>$HOME/.povray/3.6/povray.conf</code>).  POV-Ray will always use the most strict
+(<code>$HOME/.povray/3.7/povray.conf</code>).  POV-Ray will always use the most strict
 version of what is specified; user settings can only make security more strict.
 </p>
@@ Line 152: / Line 147: @@
 <p>
 Both relative and absolute paths are permitted (making <code>.</code> especially
-useful).  The install directory (typically <code>/usr/local/share/povray-3.6</code>
+useful).  The install directory (typically <code>/usr/local/share/povray-3.7</code>
-or <code>/usr/share/povray-3.6</code>) can be specified with <code>%INSTALLDIR%</code>,
+or <code>/usr/share/povray-3.7</code>) can be specified with <code>%INSTALLDIR%</code>,
 the user home directory with <code>%HOME%</code>.  The install directory and its
 descendents are typically only writable by root; therefore it does not
@@ Line 164: / Line 159: @@
 system-level restrictions, any paths specified in the system-wide
 <code>povray.conf</code> will also need to be specified in
-<code>~/.povray/3.6/povray.conf</code> if this file exists.
+<code>~/.povray/3.7/povray.conf</code> if this file exists.
 </p>

@@ Line 31: / Line 31: @@
 renderer code, and allows the Unix version to allow or deny any particular file operation.
 </p>
-<p class="Warning">
+<p class="Warning"><strong>Warning:</strong> We do not guarantee that the I/O Restriction facility will actually stop anything from
-<strong>Note:</strong>
+happening. There is always the chance that, like almost all software, it could have a bug in it that causes it to malfunction. Therefore, the onus is on the person who chooses to load an INI or scene file into POV-Ray to ensure that it does not do anything that it should not do. Please consider I/O Restrictions just a sometimes-helpful backup for manual checks.
 </p>
 <p>