[cups.general] Can't access spool folder

[Michael Sweet]

On Jun 29, 2010, at 11:32 PM, Daniel Stoeck wrote:
> ...
> "that the scheduler itself generates a fairly restrictive sandbox profile for every filter/backend subprocess it forks."
> 
> Information like this is pretty hard to find to be honest. Lucky to have a mailing list like this. You guys are supporting very very well.


Currently we have documentation on this in the Filter and Backend programming guide:

    http://www.cups.org/documentation.php/api-filter.html

although we could probably be more specific about the restrictions.  Currently you *should* be able to access both the job data (dNNNNNN-NNN) and control (cNNNNNN) files in the spool directory, but only for the current job for privacy/security reasons.

The base profile is the same as the one in:

    /System/Library/Frameworks/ApplicationServices.framework/Frameworks/PrintCore.framework/Resources/default.sb

________________________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cups.org/pipermail/cups/attachments/20100630/a1379dfd/attachment-0001.html>