Mantis Issue Tracking for Scribus
· Hosting provided by Anduin.net / Øverby Consulting ·

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0007759ScribusPDFpublic09-Jan-27 17:4309-Mar-26 12:08
Reporterdclemente 
Assigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
StatusnewResolutionopen 
PlatformOSOS Version
Product Version1.3.3.13svn 
Target VersionFixed in Version 
Summary0007759: [patch] New PDF form field: Digital signature
Description  This patch against 1.3.3.x adds a new type of form field: the digital signature field. It is a placeholder which can hold some data about the verification status of the document. An enabled viewer, like Acrobat Reader or Evince, will show some information inside that box, and will allow you to verify it when you click.
  The patch only allows you to place a signature field, but not to digitally sign the document. An external program can do this.

  The new annotation type is based in the text field and has type 14. Ideally, constants should be used instead of numbers to identify field types (see bug 7609). I followed Scribus' current style and used the number comparison.
  This function can have a better icon and more translations.

  This needs to be ported to 1.3.5. But I suggest improving bug 7609 first.
TagsNo tags attached.
Attached Filespatch file icon digital-signature.patch [^] (11,650 bytes) 09-Jan-27 17:43 [Show Content]

- Relationships
child of 0003831acknowledged Metabug: PDF Forms 

-  Notes
(0021053)
fschmid (administrator)
09-Jan-31 13:08

Sorry, i can't apply this patch because it really creates Signature fields,
but these Signatures are not vaild. They are missing the required "/V" entry,
which should contain a Digital Signature dictionary.

See the PDF Reference:
- Chapter 8.6.3 -> Signature Fields
- Chapter 8.7 Digital Signatures
(0021070)
dclemente (reporter)
09-Feb-04 12:24

This is not to digitally sign the document; for that, Scribus would have to include cryptographic libraries. This new field type is just a *placeholder* for the signature, and it is other program's job to find this field and store the digital signature there.
Library Itext could successfully sign in this way the documents I produced with my patch, and I think that Acrobat Reader too. Then this field was displayed as valid/invalid in viewers.

The /V entry seems to be optional. From the PDF 1.8 reference ( http://www.adobe.com/devnet/pdf/pdf_reference.html [^] ), page 446 (12.7.4.5 Signature Fields):

  „The field type (FT) shall be Sig, and the field value (V), if present,
shall be a signature dictionary containing the signature and specifying various attributes of the signature field (see Table 252).“
(0021071)
dclemente (reporter)
09-Feb-04 12:29

I meant PDF 1.7. But in PDF 1.5, it is the same: V is optional for the signature field.
(0021411)
dclemente (reporter)
09-Mar-26 12:08

I should make clear that users sign the PDF only *after* filling out the form; the signing process occurs thus in the PDF viewer and not in the form design tool (Scribus).

- Issue History
Date Modified Username Field Change
09-Jan-27 17:43 dclemente New Issue
09-Jan-27 17:43 dclemente File Added: digital-signature.patch
09-Jan-31 13:08 fschmid Note Added: 0021053
09-Feb-02 22:42 mhanski Relationship added child of 0003831
09-Feb-04 12:24 dclemente Note Added: 0021070
09-Feb-04 12:29 dclemente Note Added: 0021071
09-Mar-26 12:08 dclemente Note Added: 0021411



Copyright © 2000 - 2013 MantisBT Team
Powered by Mantis Bugtracker