[
https://issues.apache.org/jira/browse/TIKA-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15504023#comment-15504023
]
Nick Burch edited comment on TIKA-1997 at 9/19/16 5:07 PM:
-----------------------------------------------------------
Running your file through the openssl tool {{asn1parse}}, it shows your file as
having / being a first object of type {{pkcs7-signedData}}. It also shows the
signature from {{INFOCERT SPA}}. So, it does look to be a signed PKCS7 file,
and hence Tika appears to be doing the right thing
Unless I've mis-understood something about PKCS7 files and/or the asn1 dump
output?
was (Author: gagravarr):
Running your file through the openssl tool {{ asn1parse }}, it shows your file
as having / being a first object of type {{ pkcs7-signedData }}. It also shows
the signature from {{ INFOCERT SPA }}. So, it does look to be a signed PKCS7
file, and hence Tika appears to be doing the right thing
Unless I've mis-understood something about PKCS7 files and/or the asn1 dump
output?
> 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
(v6.3.4#6332)
