2 "$Id: api-filter.shtml 7677 2008-06-19 23:22:19Z mike $"
4 Filter and backend programming introduction for CUPS.
6 Copyright 2007-2014 by Apple Inc.
7 Copyright 1997-2006 by Easy Software Products, all rights reserved.
9 These coded instructions, statements, and computer programs are the
10 property of Apple Inc. and are protected by Federal copyright
11 law. Distribution and use rights are outlined in the file "LICENSE.txt"
12 which should have been included with this file. If this file is
13 file is missing or damaged, see the license at "http://www.cups.org/".
16 <h2 class='title'><a name="OVERVIEW">Overview</a></h2>
18 <p>Filters (which include printer drivers and port monitors) and backends
19 are used to convert job files to a printable format and send that data to the
20 printer itself. All of these programs use a common interface for processing
21 print jobs and communicating status information to the scheduler. Each is run
22 with a standard set of command-line arguments:<p>
30 <dd>The user printing the job</dd>
33 <dd>The job name/title</dd>
36 <dd>The number of copies to print</dd>
39 <dd>The options that were provided when the job was submitted</dd>
42 <dd>The file to print (first program only)</dd>
45 <p>The scheduler runs one or more of these programs to print any given job. The
46 first filter reads from the print file and writes to the standard output, while
47 the remaining filters read from the standard input and write to the standard
48 output. The backend is the last filter in the chain and writes to the
51 <p>Filters are always run as a non-privileged user, typically "lp", with no
52 connection to the user's desktop. Backends are run either as a non-privileged
53 user or as root if the file permissions do not allow user or group execution.
54 The <a href="#PERMISSIONS">file permissions</a> section talks about this in
57 <h3><a name="SECURITY">Security Considerations</a></h3>
59 <p>It is always important to use security programming practices. Filters and
60 most backends are run as a non-privileged user, so the major security
61 consideration is resource utilization - filters should not depend on unlimited
62 amounts of CPU, memory, or disk space, and should protect against conditions
63 that could lead to excess usage of any resource like infinite loops and
64 unbounded recursion. In addition, filters must <em>never</em> allow the user to
65 specify an arbitrary file path to a separator page, template, or other file
66 used by the filter since that can lead to an unauthorized disclosure of
67 information. <em>Always</em> treat input as suspect and validate it!</p>
69 <p>If you are developing a backend that runs as root, make sure to check for
70 potential buffer overflows, integer under/overflow conditions, and file
71 accesses since these can lead to privilege escalations. When writing files,
72 always validate the file path and <em>never</em> allow a user to determine
73 where to store a file.</p>
75 <blockquote><b>Note:</b>
77 <p><em>Never</em> write files to a user's home directory. Aside from the
78 security implications, CUPS is a network print service and as such the network
79 user may not be the same as the local user and/or there may not be a local home
80 directory to write to.</p>
82 <p>In addition, some operating systems provide additional security mechanisms
83 that further limit file system access, even for backends running as root. On
84 OS X, for example, no backend may write to a user's home directory. See the <a href="#SANDBOXING">Sandboxing on OS X</a> section for more information.</p>
87 <h3><a name="SIGNALS">Canceled Jobs and Signal Handling</a></h3>
89 <p>The scheduler sends <code>SIGTERM</code> when a printing job is canceled or
90 held. Filters, backends, and port monitors <em>must</em> catch
91 <code>SIGTERM</code> and perform any cleanup necessary to produce a valid output
92 file or return the printer to a known good state. The recommended behavior is to
93 end the output on the current page, preferably on the current line or object
96 <p>Filters and backends may also receive <code>SIGPIPE</code> when an upstream or downstream filter/backend exits with a non-zero status. Developers should generally ignore <code>SIGPIPE</code> at the beginning of <code>main()</code> with the following function call:</p>
99 #include <signal.h>>
104 main(int argc, char *argv[])
106 signal(SIGPIPE, SIG_IGN);
112 <h3><a name="PERMISSIONS">File Permissions</a></h3>
114 <p>For security reasons, CUPS will only run filters and backends that are owned
115 by root and do not have world or group write permissions. The recommended
116 permissions for filters and backends are 0555 - read and execute but no write.
117 Backends that must run as root should use permissions of 0500 - read and execute
118 by root, no access for other users. Write permissions can be enabled for the
121 <p>To avoid a warning message, the directory containing your filter(s) must also
122 be owned by root and have world and group write disabled - permissions of 0755
123 or 0555 are strongly encouraged.</p>
125 <h3><a name="TEMPFILES">Temporary Files</a></h3>
127 <p>Temporary files should be created in the directory specified by the
128 "TMPDIR" environment variable. The
129 <a href="#cupsTempFile2"><code>cupsTempFile2</code></a> function can be
130 used to safely create temporary files in this directory.</p>
132 <h3><a name="COPIES">Copy Generation</a></h3>
134 <p>The <code>argv[4]</code> argument specifies the number of copies to produce
135 of the input file. In general, you should only generate copies if the
136 <em>filename</em> argument is supplied. The only exception to this are
137 filters that produce device-independent PostScript output, since the PostScript
138 filter <var>pstops</var> is responsible for generating copies of PostScript
141 <h3><a name="EXITCODES">Exit Codes</a></h3>
143 <p>Filters must exit with status 0 when they successfully generate print data
144 or 1 when they encounter an error. Backends can return any of the
145 <a href="#cups_backend_t"><code>cups_backend_t</code></a> constants.</p>
147 <h3><a name="ENVIRONMENT">Environment Variables</a></h3>
149 <p>The following environment variables are defined by the printing system
150 when running print filters and backends:</p>
154 <dt>APPLE_LANGUAGE</dt>
155 <dd>The Apple language identifier associated with the job
159 <dd>The job character set, typically "utf-8".</dd>
162 <dd>When a job is submitted to a printer class, contains the name of
163 the destination printer class. Otherwise this environment
164 variable will not be set.</dd>
166 <dt>CONTENT_TYPE</dt>
167 <dd>The MIME type associated with the file (e.g.
168 application/postscript).</dd>
170 <dt>CUPS_CACHEDIR</dt>
171 <dd>The directory where cache files can be stored. Cache files can be
172 used to retain information between jobs or files in a job.</dd>
174 <dt>CUPS_DATADIR</dt>
175 <dd>The directory where (read-only) CUPS data files can be found.</dd>
177 <dt>CUPS_FILETYPE</dt>
178 <dd>The type of file being printed: "job-sheet" for a banner page and
179 "document" for a regular print file.</dd>
181 <dt>CUPS_SERVERROOT</dt>
182 <dd>The root directory of the server.</dd>
185 <dd>The device-uri associated with the printer.</dd>
187 <dt>FINAL_CONTENT_TYPE</dt>
188 <dd>The MIME type associated with the printer (e.g.
189 application/vnd.cups-postscript).</dd>
192 <dd>The language locale associated with the job.</dd>
195 <dd>The full pathname of the PostScript Printer Description (PPD)
196 file for this printer.</dd>
199 <dd>The queue name of the class or printer.</dd>
202 <dd>The recommended amount of memory to use for Raster Image
203 Processors (RIPs).</dd>
206 <dd>The directory where temporary files should be created.</dd>
210 <h3><a name="MESSAGES">Communicating with the Scheduler</a></h3>
212 <p>Filters and backends communicate with the scheduler by writing messages
213 to the standard error file. The scheduler reads messages from all filters in
214 a job and processes the message based on its prefix. For example, the following
215 code sets the current printer state message to "Printing page 5":</p>
217 <pre class="example">
220 fprintf(stderr, "INFO: Printing page %d\n", page);
223 <p>Each message is a single line of text starting with one of the following
228 <dt>ALERT: message</dt>
229 <dd>Sets the printer-state-message attribute and adds the specified
230 message to the current error log file using the "alert" log level.</dd>
232 <dt>ATTR: attribute=value [attribute=value]</dt>
233 <dd>Sets the named printer or job attribute(s). Typically this is used
234 to set the <code>marker-colors</code>, <code>marker-high-levels</code>,
235 <code>marker-levels</code>, <code>marker-low-levels</code>,
236 <code>marker-message</code>, <code>marker-names</code>,
237 <code>marker-types</code>, <code>printer-alert</code>, and
238 <code>printer-alert-description</code> printer attributes. Standard
239 <code>marker-types</code> values are listed in <a href='#TABLE1'>Table
240 1</a>. String values need special handling - see <a href="#ATTR_STRINGS">Reporting Attribute String Values</a> below.</dd>
242 <dt>CRIT: message</dt>
243 <dd>Sets the printer-state-message attribute and adds the specified
244 message to the current error log file using the "critical" log
247 <dt>DEBUG: message</dt>
248 <dd>Sets the printer-state-message attribute and adds the specified
249 message to the current error log file using the "debug" log level.</dd>
251 <dt>DEBUG2: message</dt>
252 <dd>Sets the printer-state-message attribute and adds the specified
253 message to the current error log file using the "debug2" log level.</dd>
255 <dt>EMERG: message</dt>
256 <dd>Sets the printer-state-message attribute and adds the specified
257 message to the current error log file using the "emergency" log
260 <dt>ERROR: message</dt>
261 <dd>Sets the printer-state-message attribute and adds the specified
262 message to the current error log file using the "error" log level.
263 Use "ERROR:" messages for non-persistent processing errors.</dd>
265 <dt>INFO: message</dt>
266 <dd>Sets the printer-state-message attribute. If the current log level
267 is set to "debug2", also adds the specified message to the current error
268 log file using the "info" log level.</dd>
270 <dt>NOTICE: message</dt>
271 <dd>Sets the printer-state-message attribute and adds the specified
272 message to the current error log file using the "notice" log level.</dd>
274 <dt>PAGE: page-number #-copies</dt>
275 <dt>PAGE: total #-pages</dt>
276 <dd>Adds an entry to the current page log file. The first form adds
277 #-copies to the job-media-sheets-completed attribute. The second
278 form sets the job-media-sheets-completed attribute to #-pages.</dd>
280 <dt>PPD: keyword=value [keyword=value ...]</dt>
281 <dd>Changes or adds keywords to the printer's PPD file. Typically
282 this is used to update installable options or default media settings
283 based on the printer configuration.</dd>
285 <dt>STATE: + printer-state-reason [printer-state-reason ...]</dt>
286 <dt>STATE: - printer-state-reason [printer-state-reason ...]</dt>
287 <dd>Sets or clears printer-state-reason keywords for the current queue.
288 Typically this is used to indicate persistent media, ink, toner, and
289 configuration conditions or errors on a printer.
290 <a href='#TABLE2'>Table 2</a> lists the standard state keywords -
291 use vendor-prefixed ("com.example.foo") keywords for custom states. See
292 <a href="#MANAGING_STATE">Managing Printer State in a Filter</a> for more
295 <dt>WARNING: message</dt>
296 <dd>Sets the printer-state-message attribute and adds the specified
297 message to the current error log file using the "warning" log
302 <p>Messages without one of these prefixes are treated as if they began with
303 the "DEBUG:" prefix string.</p>
305 <div class='table'><table width='80%' summary='Table 1: Standard marker-types Values'>
306 <caption>Table 1: <a name='TABLE1'>Standard marker-types Values</a></caption>
316 <td>Developer unit</td>
323 <td>fuser-cleaning-pad</td>
324 <td>Fuser cleaning pad</td>
336 <td>Photo conductor</td>
344 <td>Staple supply</td>
348 <td>Toner supply</td>
351 <td>transfer-unit</td>
352 <td>Transfer unit</td>
356 <td>Waste ink tank</td>
360 <td>Waste toner tank</td>
364 <td>Waste wax tank</td>
371 <div class='table'><table width='80%' summary='Table 2: Standard State Keywords'>
372 <caption>Table 2: <a name='TABLE2'>Standard State Keywords</a></caption>
381 <td>connecting-to-device</td>
382 <td>Connecting to printer but not printing yet.</td>
386 <td>The printer's cover is open.</td>
389 <td>input-tray-missing</td>
390 <td>The paper tray is missing.</td>
393 <td>marker-supply-empty</td>
394 <td>The printer is out of ink.</td>
397 <td>marker-supply-low</td>
398 <td>The printer is almost out of ink.</td>
401 <td>marker-waste-almost-full</td>
402 <td>The printer's waste bin is almost full.</td>
405 <td>marker-waste-full</td>
406 <td>The printer's waste bin is full.</td>
410 <td>The paper tray (any paper tray) is empty.</td>
414 <td>There is a paper jam.</td>
418 <td>The paper tray (any paper tray) is almost empty.</td>
421 <td>media-needed</td>
422 <td>The paper tray needs to be filled (for a job that is printing).</td>
426 <td>Stop the printer.</td>
430 <td>Unable to connect to printer.</td>
434 <td>The printer is out of toner.</td>
438 <td>The printer is low on toner.</td>
444 <h4><a name="ATTR_STRINGS">Reporting Attribute String Values</a></h4>
446 <p>When reporting string values using "ATTR:" messages, a filter or backend must take special care to appropriately quote those values. The scheduler uses the CUPS option parsing code for attributes, so the general syntax is:</p>
448 <pre class="example">
450 name=simple,simple,...
453 name='"complex value"','"complex value"',...
456 <p>Simple values are strings that do not contain spaces, quotes, backslashes, or the comma and can be placed verbatim in the "ATTR:" message, for example:</p>
458 <pre class="example">
459 int levels[4] = { 40, 50, 60, 70 }; /* CMYK */
461 fputs("ATTR: marker-colors=#00FFFF,#FF00FF,#FFFF00,#000000\n", stderr);
462 fputs("ATTR: marker-high-levels=100,100,100,100\n", stderr);
463 fprintf(stderr, "ATTR: marker-levels=%d,%d,%d,%d\n", levels[0], levels[1],
464 levels[2], levels[3], levels[4]);
465 fputs("ATTR: marker-low-levels=5,5,5,5\n", stderr);
466 fputs("ATTR: marker-types=toner,toner,toner,toner\n", stderr);
469 <p>Complex values that contains spaces, quotes, backslashes, or the comma must be quoted. For a single value a single set of quotes is sufficient:</p>
471 <pre class="example">
472 fputs("ATTR: marker-message='Levels shown are approximate.'\n", stderr);
475 <p>When multiple values are reported, each value must be enclosed by a set of single and double quotes:</p>
477 <pre class="example">
478 fputs("ATTR: marker-names='\"Cyan Toner\"','\"Magenta Toner\"',"
479 "'\"Yellow Toner\"','\"Black Toner\"'\n", stderr);
482 <p>The IPP backend includes a <var>quote_string</var> function that may be used to properly quote a complex value in an "ATTR:" message:</p>
484 <pre class="example">
485 static const char * /* O - Quoted string */
486 quote_string(const char *s, /* I - String */
487 char *q, /* I - Quoted string buffer */
488 size_t qsize) /* I - Size of quoted string buffer */
490 char *qptr, /* Pointer into string buffer */
491 *qend; /* End of string buffer */
495 qend = q + qsize - 5;
506 while (*s && qptr < qend)
508 if (*s == '\\' || *s == '\"' || *s == '\'')
510 if (qptr < (qend - 4))
532 <h4><a name="MANAGING_STATE">Managing Printer State in a Filter</a></h4>
534 <p>Filters are responsible for managing the state keywords they set using
535 "STATE:" messages. Typically you will update <em>all</em> of the keywords that
536 are used by the filter at startup, for example:</p>
538 <pre class="example">
539 if (foo_condition != 0)
540 fputs("STATE: +com.example.foo\n", stderr);
542 fputs("STATE: -com.example.foo\n", stderr);
544 if (bar_condition != 0)
545 fputs("STATE: +com.example.bar\n", stderr);
547 fputs("STATE: -com.example.bar\n", stderr);
550 <p>Then as conditions change, your filter sends "STATE: +keyword" or "STATE:
551 -keyword" messages as necessary to set or clear the corresponding keyword,
554 <p>State keywords are often used to notify the user of issues that span across
555 jobs, for example "media-empty-warning" that indicates one or more paper trays
556 are empty. These keywords should not be cleared unless the corresponding issue
557 no longer exists.</p>
559 <p>Filters should clear job-related keywords on startup and exit so that they
560 do not remain set between jobs. For example, "connecting-to-device" is a job
561 sub-state and not an issue that applies when a job is not printing.</p>
563 <blockquote><b>Note:</b>
565 <p>"STATE:" messages often provide visible alerts to the user. For example,
566 on OS X setting a printer-state-reason value with an "-error" or
567 "-warning" suffix will cause the printer's dock item to bounce if the
568 corresponding reason is localized with a cupsIPPReason keyword in the
569 printer's PPD file.</p>
571 <p>When providing a vendor-prefixed keyword, <em>always</em> provide the
572 corresponding standard keyword (if any) to allow clients to respond to the
573 condition correctly. For example, if you provide a vendor-prefixed keyword
574 for a low cyan ink condition ("com.example.cyan-ink-low") you must also set the
575 "marker-supply-low-warning" keyword. In such cases you should also refrain
576 from localizing the vendor-prefixed keyword in the PPD file - otherwise both
577 the generic and vendor-specific keyword will be shown in the user
582 <h4><a name="REPORTING_SUPPLIES">Reporting Supply Levels</a></h4>
584 <p>CUPS tracks several "marker-*" attributes for ink/toner supply level
585 reporting. These attributes allow applications to display the current supply
586 levels for a printer without printer-specific software. <a href="#TABLE3">Table 3</a> lists the marker attributes and what they represent.</p>
588 <p>Filters set marker attributes by sending "ATTR:" messages to stderr. For
589 example, a filter supporting an inkjet printer with black and tri-color ink
590 cartridges would use the following to initialize the supply attributes:</p>
592 <pre class="example">
593 fputs("ATTR: marker-colors=#000000,#00FFFF#FF00FF#FFFF00\n", stderr);
594 fputs("ATTR: marker-low-levels=5,10\n", stderr);
595 fputs("ATTR: marker-names=Black,Tri-Color\n", stderr);
596 fputs("ATTR: marker-types=ink,ink\n", stderr);
599 <p>Then periodically the filter queries the printer for its current supply
600 levels and updates them with a separate "ATTR:" message:</p>
602 <pre class="example">
603 int black_level, tri_level;
605 fprintf(stderr, "ATTR: marker-levels=%d,%d\n", black_level, tri_level);
608 <div class='table'><table width='80%' summary='Table 3: Supply Level Attributes'>
609 <caption>Table 3: <a name='TABLE3'>Supply Level Attributes</a></caption>
618 <td>marker-colors</td>
619 <td>A list of comma-separated colors; each color is either "none" or one or
620 more hex-encoded sRGB colors of the form "#RRGGBB".</td>
623 <td>marker-high-levels</td>
624 <td>A list of comma-separated "almost full" level values from 0 to 100; a
625 value of 100 should be used for supplies that are consumed/emptied like ink
629 <td>marker-levels</td>
630 <td>A list of comma-separated level values for each supply. A value of -1
631 indicates the level is unavailable, -2 indicates unknown, and -3 indicates
632 the level is unknown but has not yet reached capacity. Values from 0 to 100
633 indicate the corresponding percentage.</td>
636 <td>marker-low-levels</td>
637 <td>A list of comma-separated "almost empty" level values from 0 to 100; a
638 value of 0 should be used for supplies that are filled like waste ink
642 <td>marker-message</td>
643 <td>A human-readable supply status message for the user like "12 pages of
647 <td>marker-names</td>
648 <td>A list of comma-separated supply names like "Cyan Ink", "Fuser",
652 <td>marker-types</td>
653 <td>A list of comma-separated supply types; the types are listed in
654 <a href="#TABLE1">Table 1</a>.</td>
659 <h3><a name="COMMUNICATING_BACKEND">Communicating with the Backend</a></h3>
661 <p>Filters can communicate with the backend via the
662 <a href="#cupsBackChannelRead"><code>cupsBackChannelRead</code></a> and
663 <a href="#cupsSideChannelDoRequest"><code>cupsSideChannelDoRequest</code></a>
665 <a href="#cupsBackChannelRead"><code>cupsBackChannelRead</code></a> function
666 reads data that has been sent back from the device and is typically used to
667 obtain status and configuration information. For example, the following code
668 polls the backend for back-channel data:</p>
670 <pre class="example">
671 #include <cups/cups.h>
676 /* Use a timeout of 0.0 seconds to poll for back-channel data */
677 bytes = cupsBackChannelRead(buffer, sizeof(buffer), 0.0);
680 <p>Filters can also use <code>select()</code> or <code>poll()</code> on the
681 back-channel file descriptor (3 or <code>CUPS_BC_FD</code>) to read data only
682 when it is available.</p>
685 <a href="#cupsSideChannelDoRequest"><code>cupsSideChannelDoRequest</code></a>
686 function allows you to get out-of-band status information and do synchronization
687 with the device. For example, the following code gets the current IEEE-1284
688 device ID string from the backend:</p>
690 <pre class="example">
691 #include <cups/sidechannel.h>
695 <a href="#cups_sc_status_t">cups_sc_status_t</a> status;
697 /* Tell cupsSideChannelDoRequest() how big our buffer is, less 1 byte for
698 nul-termination... */
699 datalen = sizeof(data) - 1;
701 /* Get the IEEE-1284 device ID, waiting for up to 1 second */
702 status = <a href="#cupsSideChannelDoRequest">cupsSideChannelDoRequest</a>(CUPS_SC_CMD_GET_DEVICE_ID, data, &datalen, 1.0);
704 /* Use the returned value if OK was returned and the length is non-zero */
705 if (status == CUPS_SC_STATUS_OK && datalen > 0)
706 data[datalen] = '\0';
711 <h4><a name="DRAIN_OUTPUT">Forcing All Output to a Printer</a></h4>
714 <a href="#cupsSideChannelDoRequest"><code>cupsSideChannelDoRequest</code></a>
715 function allows you to tell the backend to send all pending data to the printer.
716 This is most often needed when sending query commands to the printer. For example:</p>
718 <pre class="example">
719 #include <cups/cups.h>
720 #include <cups/sidechannel.h>
723 int datalen = sizeof(data);
724 <a href="#cups_sc_status_t">cups_sc_status_t</a> status;
726 /* Flush pending output to stdout */
729 /* Drain output to backend, waiting for up to 30 seconds */
730 status = <a href="#cupsSideChannelDoRequest">cupsSideChannelDoRequest</a>(CUPS_SC_CMD_DRAIN_OUTPUT, data, &datalen, 30.0);
732 /* Read the response if the output was sent */
733 if (status == CUPS_SC_STATUS_OK)
737 /* Wait up to 10.0 seconds for back-channel data */
738 bytes = cupsBackChannelRead(data, sizeof(data), 10.0);
739 /* do something with the data from the printer */
743 <h3><a name="COMMUNICATING_FILTER">Communicating with Filters</a></h3>
745 <p>Backends communicate with filters using the reciprocal functions
746 <a href="#cupsBackChannelWrite"><code>cupsBackChannelWrite</code></a>,
747 <a href="#cupsSideChannelRead"><code>cupsSideChannelRead</code></a>, and
748 <a href="#cupsSideChannelWrite"><code>cupsSideChannelWrite</code></a>. We
749 recommend writing back-channel data using a timeout of 1.0 seconds:</p>
751 <pre class="example">
752 #include <cups/cups.h>
757 /* Obtain data from printer/device */
760 /* Use a timeout of 1.0 seconds to give filters a chance to read */
761 cupsBackChannelWrite(buffer, bytes, 1.0);
764 <p>The <a href="#cupsSideChannelRead"><code>cupsSideChannelRead</code></a>
765 function reads a side-channel command from a filter, driver, or port monitor.
766 Backends can either poll for commands using a <code>timeout</code> of 0.0, wait
767 indefinitely for commands using a <code>timeout</code> of -1.0 (probably in a
768 separate thread for that purpose), or use <code>select</code> or
769 <code>poll</code> on the <code>CUPS_SC_FD</code> file descriptor (4) to handle
770 input and output on several file descriptors at the same time.</p>
772 <p>Once a command is processed, the backend uses the
773 <a href="#cupsSideChannelWrite"><code>cupsSideChannelWrite</code></a> function
774 to send its response. For example, the following code shows how to poll for a
775 side-channel command and respond to it:</p>
777 <pre class="example">
778 #include <cups/sidechannel.h>
780 <a href="#cups_sc_command_t">cups_sc_command_t</a> command;
781 <a href="#cups_sc_status_t">cups_sc_status_t</a> status;
783 int datalen = sizeof(data);
785 /* Poll for a command... */
786 if (!<a href="#cupsSideChannelRead">cupsSideChannelRead</a>(&command, &status, data, &datalen, 0.0))
790 /* handle supported commands, fill data/datalen/status with values as needed */
793 status = CUPS_SC_STATUS_NOT_IMPLEMENTED;
798 /* Send a response... */
799 <a href="#cupsSideChannelWrite">cupsSideChannelWrite</a>(command, status, data, datalen, 1.0);
803 <h3><a name="SNMP">Doing SNMP Queries with Network Printers</a></h3>
805 <p>The Simple Network Management Protocol (SNMP) allows you to get the current
806 status, page counter, and supply levels from most network printers. Every
807 piece of information is associated with an Object Identifier (OID), and
808 every printer has a <em>community</em> name associated with it. OIDs can be
809 queried directly or by "walking" over a range of OIDs with a common prefix.</p>
811 <p>The two CUPS SNMP functions provide a simple API for querying network
812 printers through the side-channel interface. Each accepts a string containing
813 an OID like ".1.3.6.1.2.1.43.10.2.1.4.1.1" (the standard page counter OID)
814 along with a timeout for the query.</p>
816 <p>The <a href="#cupsSideChannelSNMPGet"><code>cupsSideChannelSNMPGet</code></a>
817 function queries a single OID and returns the value as a string in a buffer
820 <pre class="example">
821 #include <cups/sidechannel.h>
824 int datalen = sizeof(data);
826 if (<a href="#cupsSideChannelSNMPGet">cupsSideChannelSNMPGet</a>(".1.3.6.1.2.1.43.10.2.1.4.1.1", data, &datalen, 5.0)
827 == CUPS_SC_STATUS_OK)
829 /* Do something with the value */
830 printf("Page counter is: %s\n", data);
835 <a href="#cupsSideChannelSNMPWalk"><code>cupsSideChannelSNMPWalk</code></a>
836 function allows you to query a whole group of OIDs, calling a function of your
837 choice for each OID that is found:</p>
839 <pre class="example">
840 #include <cups/sidechannel.h>
843 my_callback(const char *oid, const char *data, int datalen, void *context)
845 /* Do something with the value */
846 printf("%s=%s\n", oid, data);
853 <a href="#cupsSideChannelSNMPWalk">cupsSNMPSideChannelWalk</a>(".1.3.6.1.2.1.43", 5.0, my_callback, my_data);
856 <h2><a name="SANDBOXING">Sandboxing on OS X</a></h2>
858 <p>Starting with OS X 10.6, filters and backends are run inside a security "sandbox" which further limits (beyond the normal UNIX user/group permissions) what a filter or backend can do. This helps to both secure the printing system from malicious software and enforce the functional separation of components in the CUPS filter chain. What follows is a list of actions that are explicitly allowed for all filters and backends:</p>
862 <li>Reading of files: pursuant to normal UNIX file permissions, filters and backends can read files for the current job from the <var>/private/var/spool/cups</var> directory and other files on mounted filesystems <em>except</em> for user home directories under <var>/Users</var>.</li>
864 <li>Writing of files: pursuant to normal UNIX file permissions, filters and backends can read/write files to the cache directory specified by the <code>CUPS_CACHEDIR</code> environment variable, to the state directory specified by the <code>CUPS_STATEDIR</code> environment variable, to the temporary directory specified by the <code>TMPDIR</code> environment variable, and under the <var>/private/var/db</var>, <var>/private/var/folders</var>, <var>/private/var/lib</var>, <var>/private/var/mysql</var>, <var>/private/var/run</var>, <var>/private/var/spool</var> (except <var>/private/var/spool/cups</var>), <var>/Library/Application Support</var>, <var>/Library/Caches</var>, <var>/Library/Logs</var>, <var>/Library/Preferences</var>, <var>/Library/WebServer</var>, and <var>/Users/Shared</var> directories.</li>
866 <li>Execution of programs: pursuant to normal UNIX file permissions, filters and backends can execute any program not located under the <var>/Users</var> directory. Child processes inherit the sandbox and are subject to the same restrictions as the parent.</li>
868 <li>Bluetooth and USB: backends can access Bluetooth and USB printers through IOKit. <em>Filters cannot access Bluetooth and USB printers directly.</em></li>
870 <li>Network: filters and backends can access UNIX domain sockets under the <var>/private/tmp</var>, <var>/private/var/run</var>, and <var>/private/var/tmp</var> directories. Backends can also create IPv4 and IPv6 TCP (outgoing) and UDP (incoming and outgoing) socket, and bind to local source ports. <em>Filters cannot directly create IPv4 and IPv6 TCP or UDP sockets.</em></li>
872 <li>Notifications: filters and backends can send notifications via the Darwin <code>notify_post()</code> API.</li>
876 <blockquote><b>Note:</b> The sandbox profile used in CUPS 2.0 still allows some actions that are not listed above - these privileges will be removed over time until the profile matches the list above.</blockquote>