Open
Bug 1295109
Opened 9 years ago
Updated 3 years ago
Directly send PDF file to OS's spool module when possible
Categories
(Core :: Printing: Output, defect)
Tracking
()
NEW
People
(Reporter: jj.evelyn, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
On Linux(and maybe OS X), they allows application send PDF file to its spool module directly. If Gecko supports this, it might be more efficient to print PDF.
Check that we correctly handle the PDF forms scenario.
| Reporter | ||
Comment 2•9 years ago
|
||
This link might be useful to understand linux's spooling module.
https://notehub.org/w88ic
Comment 3•9 years ago
|
||
(In reply to Evelyn Hung [:evelyn] from comment #0)
> On Linux(and maybe OS X), they allows application send PDF file to its spool
> module directly. If Gecko supports this, it might be more efficient to print
> PDF.
For OS X, see the code that bug 1309272 part 8 adds to nsDeviceContextSpecX::EndDocument (specifically the PMPrinterPrintWithFile call).
Comment 4•8 years ago
|
||
What are the security implications of sending possibly malicious PDF directly to the OS (without sanitizing it)?
| Reporter | ||
Comment 5•8 years ago
|
||
Hmm... I know PDFium can rewrite the to-be-printed-PDF and pass out a new binary to its caller. Not sure how effective it removes those malicious scripts. :-/
Updated•8 years ago
|
Blocks: pdf-printing
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•