[
https://issues.apache.org/jira/browse/TIKA-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883273#comment-17883273
]
ASF GitHub Bot commented on TIKA-4309:
--------------------------------------
alexey-pelykh commented on PR #1947:
URL: https://github.com/apache/tika/pull/1947#issuecomment-2363784208
> The magic for MachO is cefaedfe (32 bit) or cffaedfe (64 bit) as the first
four bytes?
```
/* Constant for the magic field of the mach_header_64 (64-bit architectures)
*/
#define MH_MAGIC_64 0xfeedfacf /* the 64-bit mach magic number */
#define MH_CIGAM_64 0xcffaedfe /* NXSwapInt(MH_MAGIC_64) */
```
and
```
/* Constant for the magic field of the mach_header (32-bit architectures) */
#define MH_MAGIC 0xfeedface /* the mach magic number */
#define MH_CIGAM 0xcefaedfe /* NXSwapInt(MH_MAGIC) */
```
> Should we treat a fat machO file like a container file and parse its
individual components as separate files? I'm not very familiar with this file
type, and I'm happy for a "no!"
It's truly a container, and we can do that - a link to an example would be
helpful :) In test files, it contains two separate "almost-mach-o" blobs
> ExecutableParser: support MachO
> -------------------------------
>
> Key: TIKA-4309
> URL: https://issues.apache.org/jira/browse/TIKA-4309
> Project: Tika
> Issue Type: New Feature
> Reporter: Alexey Pelykh
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
