SAPP stands for Simple and Agnostic PDF Parser and it makes what is name says: parsing PDF files. It also enables other cool features such as rebuilding documents (to make the content more clear or compact) or digitally signing documents.
SAPP is agnostic because it does not care of composing PDF documents (e.g. adding pages, updating pages, etc.). Instead, its aim is to be somehow a backend to parse an existing PDF document and to manipulate the objects included on it, or to create new ones.
The way of working with SAPP can be seen in the function to sign the document: it is an independent function that adds and manipulates the PDF objects contained in the document.
Some of the features of SAPP:
- Supports 1.4 PDF documents
- Supports many features of 1.5 PDF and later documents (including cross-reference streams)
- Works using incremental versions
- Works for rebuilding documents to flatten versions (older version are dropped)
- Signature of documents using the Acrobat workflow (and obtain the green checkmark).
- Others.
I created SAPP because I wanted to programmatically sign documents, including multiple signatures.
I tried tcpdf along with FPDI, but the results are not those expected. When importing a document using FPDI, the result is a new document with the pages of the original one, not the original document. So if the original document was signed, those signatures were lost.
I read about SetaPDF-Signer, but it cannot be used for free. I also inspected some CLI tools such as PortableSigner, but (1) it was Java based (and I really don't like java) and (2) it depends on iText and other libraries which don't seem to be free at this moment.
At the end I got the PDF 1.7 definition, and I learned about incremental PDF documents and its utility to include multiple signature in documents.
To use SAPP in your projects, you just need to use composer:
$ composer require ddn/sapp:dev-mainThen, a vendor folder will be created, and then you can simply include the main file and use the classes:
use ddn\sapp\PDFDoc;
require_once('vendor/autoload.php');
$obj = PDFDoc::from_string(file_get_contents("/path/to/my/pdf/file.pdf"));
echo $obj->to_pdf_file_s(true);Altenatively you can clone the repository and use composer:
$ git clone https://github.com/dealfonso/sapp
$ cd sapp
$ composer dump-autoload
$ php pdfrebuild.php examples/testdoc.pdf > testdoc-rebuilt.pdfThen you will be ready to include the main file and use the classes.
In the root folder of the source code you can find two simple examples:
pdfrebuild.php: this example gets a PDF file, loads it and rebuilds it to make every PDF object to be in order, and also reducing the amount of text to define the document.pdfsign.php: this example gets a PDF file and digitally signs it using a pkcs12 (pfx) certificate.pdfsigni.php: this example gets a PDF file and digitally signs it using a pkcs12 (pfx) certificate, and adds an image that makes visible the signature in the document.pdfcompare.php: this example compares two PDF files and checks the differences between them (object by object, field by field).
Once cloned the repository and generated the autoload content, it is possible to run the example:
$ php pdfrebuild.php examples/testdoc.pdf > testdoc-rebuilt.pdfThe result is a more ordered PDF document which is (problably) smaller. (e.g. rebuilding examples/testdoc.pdf provides a 50961 bytes document while the original was 51269 bytes).
$ ls -l examples/testdoc.pdf
-rw-r--r--@ 1 calfonso staff 51269 5 nov 14:01 examples/testdoc.pdf
$ ls -l testdoc-rebuilt.pdf
-rw-r--r--@ 1 calfonso staff 50961 5 nov 14:22 testdoc-rebuilt.pdf
And the xref table looks significantly better ordered:
$ cat examples/testdoc.pdf
...
xref
0 39
0000000000 65535 f
0000049875 00000 n
0000002955 00000 n
0000005964 00000 n
0000000022 00000 n
0000002935 00000 n
0000003059 00000 n
0000005928 00000 n
...
$ cat testdoc-rebuilt.pdf
...
xref
0 8
0000000000 65535 f
0000000009 00000 n
0000000454 00000 n
0000000550 00000 n
0000000623 00000 n
0000003532 00000 n
0000003552 00000 n
0000003669 00000 n
...
The code:
use ddn\sapp\PDFDoc;
require_once('vendor/autoload.php');
if ($argc !== 2)
fwrite(STDERR, sprintf("usage: %s <filename>", $argv[0]));
else {
if (!file_exists($argv[1]))
fwrite(STDERR, "failed to open file " . $argv[1]);
else {
$obj = PDFDoc::from_string(file_get_contents($argv[1]));
if ($obj === false)
fwrite(STDERR, "failed to parse file " . $argv[1]);
else
echo $obj->to_pdf_file_s(true);
}
}To sign a PDF document, it is possible to use the script pdfsign.php:
$ php pdfsign.php examples/testdoc.pdf caralla.p12 > testdoc-signed.pdfAnd now the document is signed. And if you wanted to add a second signature, it is as easy as signing the resulting document again:
$ php pdfsign.php testdoc-signed.pdf user.p12 > testdoc-resigned.pdfThe code: (full working example)
use ddn\sapp\PDFDoc;
require_once('vendor/autoload.php');
if ($argc !== 3)
fwrite(STDERR, sprintf("usage: %s <filename> <certfile>", $argv[0]));
else {
if (!file_exists($argv[1]))
fwrite(STDERR, "failed to open file " . $argv[1]);
else {
// Silently prompt for the password
fwrite(STDERR, "Password: ");
system('stty -echo');
$password = trim(fgets(STDIN));
system('stty echo');
fwrite(STDERR, "\n");
$file_content = file_get_contents($argv[1]);
$obj = PDFDoc::from_string($file_content);
if ($obj === false)
fwrite(STDERR, "failed to parse file " . $argv[1]);
else {
if (!$obj->set_signature_certificate($argv[2], $password)) {
fwrite(STDERR, "the certificate is not valid");
} else {
$docsigned = $obj->to_pdf_file_s();
if ($docsigned === false)
fwrite(STDERR, "could not sign the document");
else
echo $docsigned;
}
}
}
}To sign a PDF document that contains an image associated to the signature, it is possible to use the script pdfsigni.php:
$ php pdfsigni.php examples/testdoc.pdf "https://www.google.es/images/branding/googlelogo/1x/googlelogo_color_272x92dp.png" caralla.p12 > testdoc-signed.pdfAnd now the document is signed, and a cool image appears. If you wanted to add a second signature, it is as easy as signing the resulting document again.
The main difference with the previous code is the next:
The code:
* the code related to the position in which the signature and the image appear has been ommited, but can be seen in file pdfsigni.php.
...
$obj->set_signature_appearance(0, [ $p_x, $p_y, $p_x + $i_w, $p_y + $i_h ], $image);
if (!$obj->set_signature_certificate($argv[3], $password)) {
fwrite(STDERR, "the certificate is not valid");
} else {
$docsigned = $obj->to_pdf_file_s();
if ($docsigned === false)
fwrite(STDERR, "could not sign the document");
else
echo $docsigned;
}
...This is an example of how to manipulate the objects in a document. The example walks over any object in the document, obtains its stream deflated, removes the filter (i.e. compression method), and restores it to the document. So that the objects are not compressed anymore (e.g. you can read in plain text the commands used to draw the elements).
The code:
foreach ($obj->get_object_iterator() as $oid => $object) {
if ($object === false)
continue;
if ($object["Filter"] == "/FlateDecode") {
/* Getting the stream with raw flag set to "false" will process the stream prior to returning it */
$stream = $object->get_stream(false);
if ($stream !== false) {
unset($object["Filter"]);
/* Setting the stream with raw flag set to "false" will process the stream, although in this case it is not important, because we removed the filter.*/
$object->set_stream($stream, false);
$obj->add_object($object);
}
}
}
echo $obj->to_pdf_file_s(true);At this time, the main limitations are:
- Basic support for non-zero generation pdf objects: they are uncommon, but according to the definition of the PDF structure, they are possible. If you find one non-zero generation object please send me the document and I'll try to support it.
- Not dealing with encrypted documents.
- Other limitations, for sure :)
My idea is to provide support for other cool features:
- Support for TSA timestamping
- Include document protection (i.e. lock documents)
- Document encryption (http://www.fpdf.org/en/script/script37.php)
- Try to provide support to write some text
- The mechanism for calculating the signature hash is heavily inspired in tcpdf.
- Reading jpg and png files has been taken from fpdf.