Dashboard › fossilize › Distillation
Distillation
ID: 1cb8c4d6-e690-4346-96b4-c2d53b8ae54b
Generation: 0
Tokens: 325
R_compression: 11.781
C_norm: 0.000
Archived: No
Created: 2026-06-09 14:29:43
Source IDs:
["adcac4c6a4f24c5fac8df989f65e314f","984039e9dc266b1293c8d22fc1ab6b70"]
Observations
<observations>
Date: June 9, 2026
- 🟡 (11:46) User asked for detailed research report on macOS binary signing and Gatekeeper behavior, covering 10 topics:
- Gatekeeper behavior with unsigned binaries (unsigned vs. ad-hoc vs. self-signed differences; which get killed vs. show dialog)
- Ad-hoc signing (
codesign -s -) — whether it helps with Gatekeeper for downloaded binaries
- Self-signed certificate signing — process and UX difference vs. unsigned
- Apple Developer ID signing WITHOUT notarization — what happens
- Apple Developer ID signing WITH notarization — full process and UX
com.apple.quarantine extended attribute — interaction with each signing level; bypass via xattr -d com.apple.security.quarantinefossilize npm package sign: true option — what signing capabilities it has (sources: https://www.npmjs.com/package/fossilize and https://github.com/nicolo-ribaudo/fossilize)- Node.js SEA (Single Executable Application)