`file -b` reports `data` for an XML plist containing a control character
or NUL byte, which CoreFoundation still reads. plistSourceFormat only
probed the source for markup when `file` reported text, so these sources
were labelled `unknown` and skipped REA's XML reader. When that reader
would have refused them, the result also lacked the limitation that says
the value came from plutil's conversion. Two plists shipped with macOS
27.2.1 are affected.
Probe the source prefix for any description that does not name binary,
XML or JSON. Such XML now takes the same route as XML that `file`
recognizes: REA's reader decodes it directly, or #12251's plutil fallback
records REA's refusal reason. OpenStep and other non-markup sources stay
`unknown`.
OpenPGP packet headers read their one-, two- and four-byte lengths with
raw Buffer reads after the header-width checks. Read them through an
openpgp BinaryReader. This was the last counted raw numeric read, so the
raw-buffer-read baseline is removed and the guard now refuses any new
copy outright. The CI change-scope test names another baseline file as
its static-only path.
Refs #11865
Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
A binary plist UID projects as `{ UID: n }` and the XML convention as
`{ CF$UID: n }`, so the structural check accepted a UID-valued $top as the
roots dictionary. A plist naming another archiver with such a $top was then
decoded with an invented root named after the UID key. The kind test now
also requires that $top is not a UID. NSKeyedArchiver archives keep their
existing $top handling.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Keyed archives may now name another archiver, so the name is source
metadata a caller needs: a SceneKit scene says SCNKeyedArchiver. The
keyed-archive result gains `archiver`, the declared `$archiver` string, and
the inspect_keyed_archive contract describes archives written by
NSKeyedArchiver or a subclass archiver such as SCNKeyedArchiver instead of
NSKeyedArchiver plists only.
The reviewed golden graph adds `"archiver": "NSKeyedArchiver"` for its
capture; only its provenance digest changes, and the captured XML does not.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Foundation's NSKeyedUnarchiver decodes a keyed archive whatever its
$archiver names. SceneKit writes .scn scenes with SCNKeyedArchiver, so
inspect_keyed_archive refused system and third-party scenes such as Audio
MIDI Setup's SpeakerRoom.scn as "not an NSKeyedArchiver archive" and pointed
the caller at inspect_plist.
An archive named NSKeyedArchiver keeps its current handling, including
format failures for a damaged table. Another string archiver name is a keyed
archive when the plist also has an $objects table and $top roots; without
them it stays an ordinary property list with the inspect_plist workflow.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(artifacts): keep a ZIP inventory when one member uses an unsupported compression method
zip.js refuses a member whose compression method it has no codec for, such
as bzip2 (12) or LZMA (14), before reading its data. typedZipFailure turned
that refusal into an archive-level unavailable failure, so inventory_artifact,
inspect_artifact and compare_artifacts rejected the whole archive and never
listed or hashed its readable members. unzip and bsdtar list them all.
A refusal raised while reading one member is now ArtifactEntryContentUnavailable,
the per-member failure the inventory scan already records, as UnityFS members
with unsupported compression do. The member keeps its occurrence with an
unavailable hash and a limitation naming the method, siblings are hashed, and
coverage is unknown. Extraction of that member is still refused.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(artifacts): keep ZIP entry coverage complete for an unreadable member codec
The central directory still lists every entry when one member's compression
method is unsupported; only that member's content is unreadable. Recording an
unknown traversal made inventory coverage, whose scope is container entries,
claim that entries might be missing. Drop the traversal override, as the
encrypted-member path already does, and let the occurrence limitation carry
the content gap.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
CUBIN kernel names were always decoded as Latin-1, so a valid UTF-8
symbol such as kérnel_日本 was reported as mojibake while inspection
stayed complete. Reuse the ELF name decoding owned by native exports:
keep valid UTF-8, fall back to lossless Latin-1 otherwise, and disclose
the fallback with the original bytes as a kernel limitation.
Co-authored-by: Anurag Singh <211784907+Anurag-5ingh@users.noreply.github.com>