<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jun 30, 2010, at 8:33 AM, Helge Blischke wrote:</div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000">...<br></font>According to the source code in scheduLER/process.c (cups 1.4.4), read <br>access to the spool directory is generally denied and, for the current job, <br>reading only the data file is allowed.<br><br>Shall I file a bug for this?<br></div></blockquote></div><div><br></div>The specific rule for accessing spool files is:<div><br></div><div><div> if (job_id)</div><div> cupsFilePrintf(fp,</div><div> "(allow file-read-data file-read-metadata\n"</div><div> " (regex #\"^%s/([ac]%05d|d%05d-[0-9][0-9][0-9])$\"))\n",</div><div> request, job_id, job_id);</div><div><br></div><div>which means any aNNNNNN (authentication data), cNNNNNN (control file), or dNNNNNN-MMM (job data) file in the spool directory where NNNNNN is the job ID.</div><div><br></div><div>If the backend is getting a sandboxd deny message when accessing the control file for that job or if the backend is unable to read the control file for that job, that would be a bug worth reporting. However, we don't recommend reading the control files directly since the format (and location) are subject to change and are not part of the filter/backend interface we support.</div><div><br></div><div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>________________________________________________________________________</div><div>Michael Sweet, Senior Printing System Engineer, PWG Chair</div><div><br></div></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br></div></body></html>