Apparency 2.3
Mothers Ruin Software (Mastodon):
Changed the info pane to show Quarantine rather than Downloaded. Modern macOS likes to quarantine files that are opened by a sandboxed app, seemingly resulting in more non-download quarantines than actual downloads. You can still click on the quarantine date here to see what app triggered it and how — for example, “Downloaded by Safari” (for a true download) or “Opened by Hex Editor” (for a sandboxed app). If the quarantine has already triggered a Gatekeeper prompt (and you proceeded with opening the item anyway, in whatever tortured way macOS now requires), the quarantine text is grayed out.
[…]
Added the linker-assigned UUID to the Executable Information inspector.
This is what Local Network Privacy uses.
The appy command line tool has a new
‑‑show-components(-c) option, to show the details of an app’s components right in Terminal, without launching the Apparency app. This gives information such as bundle identifiers, versions, signing identities, and various flags (Gatekeeper, notarization, etc), all in a single plain text table. You can customize which columns are included using the‑‑add-column(-C) option.
Previously:
- Archaeology 1.3
- Gatekeeper Change in macOS 15.4
- Local Network Privacy on Sequoia
- Sequoia Removes Gatekeeper Contextual Menu Override
- Quarantine: Apps and Documents
- Persistent File Access via com.apple.macl Xattr
- Sandboxing Makes Quarantine Flags Almost Meaningless
- Max Inspect 1.0
2 Comments RSS · Twitter · Mastodon
>Note that, although this UUID will change when the code and/or build environment change, it is actually stable when building the same code using the same tools on the same OS version. As the ld(1) man page says, “by default the linker generates the UUID of the output file based on a hash of the output file's content.”
So they’re numbers that happen to be parseable as a quasi-UUID?
(It does seem like it. Looking at a few crash reports over the years, one pretended to be version 6, two version 3, one version 4.)
@Sören, I didn't try to grok the algorithm, but it *is* in the open source ld64 component, if you're interested:
