This is an automated email from the ASF dual-hosted git repository.
asf-gitbox-commits pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/pdfbox-docs.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 0ce18b91 Site checkin for project Apache PDFBox Website
0ce18b91 is described below
commit 0ce18b910eb44fce7220e246b739d4aef2e73797
Author: Maruan Sahyoun <[email protected]>
AuthorDate: Wed Aug 26 12:59:01 2026 +0200
Site checkin for project Apache PDFBox Website
---
content/2.0/faq.html | 12 ++++++++++++
content/3.0/faq.html | 12 ++++++++++++
2 files changed, 24 insertions(+)
diff --git a/content/2.0/faq.html b/content/2.0/faq.html
index 6b5edcd3..fb250730 100644
--- a/content/2.0/faq.html
+++ b/content/2.0/faq.html
@@ -293,6 +293,15 @@ the command-line app.</p>
are written into a larger zero-allocated area.
The fix is to wrap the byte array retrieved from
<code>PDSignature.getContents()</code>
into a <code>ByteArrayInputStream</code> before passing it to the
<code>CMSSignedData</code> constructor.</p>
+<h3 id="how-can-i-check-signed-pdfs%3F" tabindex="-1">How can I check signed
PDFs?</h3>
+<p>Parsing does not include the verification or the validation of electronic
signatures.
+This applies to certification constraints (DocMDP) and usage rights (UR3) as
well.
+The ShowSignature example does a partial verification and validation,
+but it can't detect allowed or forbidden changes, annd UR3 isn't supported at
all.
+Certificates are checked up to the root certificate,
+but it does not check the root certificate against AATL and EUTL.
+This is mostly a developer tool to create your own.
+The gold standard is Adobe Reader.</p>
</section>
<aside>
@@ -403,6 +412,9 @@ into a <code>ByteArrayInputStream</code> before passing it
to the <code>CMSSigne
<li><a
href="#ioexception%3A-extra-data-detected-in-stream">IOException: Extra data
detected in stream</a>
</li>
+
+ <li><a href="#how-can-i-check-signed-pdfs%3F">How can I
check signed PDFs?</a>
+ </li>
</ol>
</li>
</ol>
diff --git a/content/3.0/faq.html b/content/3.0/faq.html
index 4cd76c0c..4f2cb5f5 100644
--- a/content/3.0/faq.html
+++ b/content/3.0/faq.html
@@ -302,6 +302,15 @@ the command-line app.</p>
are written into a larger zero-allocated area.
The fix is to wrap the byte array retrieved from
<code>PDSignature.getContents()</code>
into a <code>ByteArrayInputStream</code> before passing it to the
<code>CMSSignedData</code> constructor.</p>
+<h3 id="how-can-i-check-signed-pdfs%3F" tabindex="-1">How can I check signed
PDFs?</h3>
+<p>Parsing does not include the verification or the validation of electronic
signatures.
+This applies to certification constraints (DocMDP) and usage rights (UR3) as
well.
+The ShowSignature example does a partial verification and validation,
+but it can't detect allowed or forbidden changes, annd UR3 isn't supported at
all.
+Certificates are checked up to the root certificate,
+but it does not check the root certificate against AATL and EUTL.
+This is mostly a developer tool to create your own.
+The gold standard is Adobe Reader.</p>
</section>
<aside>
@@ -415,6 +424,9 @@ into a <code>ByteArrayInputStream</code> before passing it
to the <code>CMSSigne
<li><a
href="#ioexception%3A-extra-data-detected-in-stream">IOException: Extra data
detected in stream</a>
</li>
+
+ <li><a href="#how-can-i-check-signed-pdfs%3F">How can I
check signed PDFs?</a>
+ </li>
</ol>
</li>
</ol>
