tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alessandro Scaldaferro (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-1997) Problem in Tika().detect for xml file signed in CADES
Date Thu, 08 Jun 2017 09:39:18 GMT

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

Alessandro Scaldaferro commented on TIKA-1997:

In https://www.ietf.org/rfc/rfc2633.txt I've found the following infos:
   MIME Type                                                File Extension
   Application/pkcs7-mime (signedData,      .p7m

   Application/pkcs7-mime (degenerate       .p7c
   signedData "certs-only" message)

   Application/pkcs7-signature                      .p7s

Looks like .p7m files are signed file (the original file + the signature data), and .p7s files
are "signature files" containing only the signature data but not the original file.

> Problem in Tika().detect for xml file signed in CADES
> -----------------------------------------------------
>                 Key: TIKA-1997
>                 URL: https://issues.apache.org/jira/browse/TIKA-1997
>             Project: Tika
>          Issue Type: Sub-task
>          Components: detector
>    Affects Versions: 1.13
>         Environment: JDK 1.7
>            Reporter: Michele Andreano
>            Priority: Blocker
>         Attachments: test.xml.p7m
> When I submit a tika a xml file signed in P7M format, I expect tika return as mimetype
application / pkcs7-mime instead gives me application / pkcs7-signature.
> How is it possible?

This message was sent by Atlassian JIRA

View raw message