From: Till Kamppeter <till.kamppeter@gmail.com>
To: "The CUPS user discussion list." <cups@cups.org>,
Open Printing <printing-architecture@lists.linux-foundation.org>
Subject: [Printing-architecture] CUPS 2.2.x drops interface scripts - How to create filtered queues without PPD
Date: Tue, 14 Jun 2016 19:53:54 -0300 [thread overview]
Message-ID: <57608B02.1040802@gmail.com> (raw)
Hi,
I have seen now the new features list of the first beta of the CUPS
2.2.x series and one of the changes is
- Interface scripts are no longer supported for security reasons
(<rdar://problem/23135640>)
System V interface scripts give a possibility to create filtered print
queues without PPD.
I make use of this in cups-filters. If cups-browsed discovers an IPP
network printer (with "CreateIPPPrinterQueues Yes" in cups-browsed.conf)
and is not able to gather enough info via IPP for making a PPD for this
printer, it creates a queue with interface script, the script calling
the filter sys5ippprinter which in turn calls all filters to convert the
input format (PDF, JPEG, or PWG Raster) into the printer's native format
(PWG Raster, PDF, PostScript, PCL-XL, or PCL 5c/e).
By the way, PPD files are also on the way to get deprecated.
Now I have some questions about what to do:
- How will I do non-raw (filtered) queues without PPD files?
- Or should cups-browsed always generate PPD files, using certain
default values for capability info which it is not able to obtain
from the printer?
- What were the security reasons leading to remove the interface script
support from CUPS? It seems that this got only discussed internally
at Apple.
- And if there are neither interface scripts nor PPD files (probably
this requires all printers being IPP Everywhere), how will CUPS
determine which filters to run?
Till
reply other threads:[~2016-06-14 22:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57608B02.1040802@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=cups@cups.org \
--cc=printing-architecture@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.