It may be that I'm sticking out my head here but I question the assignment of this bug as grave.
Certainly there is a problem with the default configuration if a user wishes to include files installed somewhere in /usr/ as the default configuration prohibits that. But remember that it is a configuration issue, most users can use sudo to change it or perhaps ask their sysadmin to do it. For the case of terraform, it may be done by adding the line read* = /usr/share/terraform somewhere in /etc/povray/3.6/povray.conf But for users of povray who do not try to include files from directories which are configured by default to be inaccessible, the current povray package does function properly. We should also keep in mind that the current default configuration is similar to the default configuration obtained when one does compile and install PoV-Ray from source directly. In summary, the reported problem does not render the package unusable, it does not cause data loss, or introduce a security hole when installed. Thus it is appropriate with a lower severity level than grave. Important, normal or even minor, could all be considered. The possibility of restricting file access beyond the permissions of the file system was introduced in PoV-Ray 3.5 for reasons explained in the PoV-Ray manual. Based on the standard for placing files in the file system, files of type .inc or .pov included in a Debian package, would normally be placed somewhere in /usr. To ease the coexistence of other Debian packages with functionality for PoV-Ray, it could therefore be a good thing to include the whole /usr hierarchy as readable in the default configuration. This means the lines read* = /usr/share/povray/include read* = /usr/share/povray/scenes in /etc/povray/3.6/povray.conf would be replaced by read* = /usr Anders -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
