pdfbox-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tilman Hausherr (Jira)" <j...@apache.org>
Subject [jira] [Commented] (PDFBOX-3492) Remove classic signing and keep external signing only
Date Mon, 07 Oct 2019 19:08:00 GMT

    [ https://issues.apache.org/jira/browse/PDFBOX-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16946152#comment-16946152

Tilman Hausherr commented on PDFBOX-3492:

LOL, I created this ticket and today I don't consider it THAT important, nor do I remember
it. Maybe there was a discussion about it.

External signing means that the signing can be done by an outside application. However the
external-signing-code, as it is now, can also be used without having an outside application.
See the CreateSignature examples. I suspect that my thought was to have the code only once,
because it is two different paths to do the same thing, so we could dump the "old style".
In the sample code you'll see that the signing method is always the same.

> Remove classic signing and keep external signing only
> -----------------------------------------------------
>                 Key: PDFBOX-3492
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-3492
>             Project: PDFBox
>          Issue Type: Sub-task
>          Components: Signing
>    Affects Versions: 3.0.0 PDFBox
>            Reporter: Tilman Hausherr
>            Priority: Major
>             Fix For: 3.0.0 PDFBox
> to be done later, lets first wait for feedback on the external signing.

This message was sent by Atlassian Jira

To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org

View raw message