You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Matthias Hofbauer (Jira)" <ji...@apache.org> on 2022/06/02 12:31:00 UTC
[jira] [Created] (TIKA-3784) Detector return "application/x-x509-key" when scanning a .p12 file
Matthias Hofbauer created TIKA-3784:
---------------------------------------
Summary: Detector return "application/x-x509-key" when scanning a .p12 file
Key: TIKA-3784
URL: https://issues.apache.org/jira/browse/TIKA-3784
Project: Tika
Issue Type: Bug
Components: detector
Affects Versions: 1.26
Reporter: Matthias Hofbauer
We are using tika to check if the MIME type of the file extensions matches with the MIME type of the file content.
After our upgrade from tika-core 1.22 to 1.26 our logic does not work anymore for certificates of type .p12, .pfx, .cer, .der.
For the .p12 and .pfx extension the MIME type is "application/x-pkcs12" but the tika detector returns "application/x-x509-key" instead.
After checking the tika-mimetype.xml and comparing it to my .p12 file I found the following MIME magic which explains why I got these types back.
{code:xml}
<mime-type type="application/x-x509-key;format=der">
<sub-class-of type="application/x-x509-key"/>
<!-- These are just a bunch of magic integers as defined by the key format... -->
<!-- Always seem to have a version integer as their first entry, -->
<!-- normally 00, 01 or 02, check for that -->
<magic priority="40">
<match value="0x3081FF020100" type="string"
mask="0xFFFF00FFFFFC" offset="0"/>
<match value="0x3082FFFF020100" type="string"
mask="0xFFFF0000FFFFFC" offset="0"/>
</magic>
</mime-type> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)