# macOS local network access CH-J Server Manager requests local network access when you connect to a local SSH server. Allow the macOS prompt. If access was denied, enable CH-J Server Manager in **System Settings → Privacy & Security → Local Network**, then connect again. The app cannot override this choice. ## Packaging Electron ships prebuilt launchers with shared Mach-O UUIDs. macOS uses these UUIDs when identifying applications for local network access. `afterPack.js` therefore assigns application-specific UUIDs to the main launcher and Electron helper launchers **before signing**. The UUIDs include the bundle identity, launcher path, architecture and packaged `app.asar` digest. Repeating packaging of the same payload preserves its UUIDs; a different payload gets different UUIDs without changing the application version or bundle identifier. `packageMacInstaller.js` also prepares this identity when invoked directly, prefers an installed Developer ID Application identity over an ad-hoc signature, and checks the UUIDs, bundle ID, unchanged application version, local network usage description and code signature in the final mounted DMG. Without a Developer ID Application certificate it produces an ad-hoc test build. An Apple Development certificate is not a Developer ID distribution certificate. Only the small main/helper launchers are patched. Their original Electron dSYMs will no longer match; Electron Framework and its UUID/debugging symbols remain unchanged. Installed apps and older build copies are never modified by this packaging step. Run `npm run build:mac` to produce the corrected installer. Install that build and launch it from Finder to test local network access. A packaging smoke test or `npm start` inherits Terminal's network access and cannot verify the Finder permission prompt. Multiple installed copies can still confuse macOS permission settings; do not use a global privacy reset or disable system protections. References: [Apple TN3179](https://developer.apple.com/documentation/technotes/tn3179-understanding-local-network-privacy), [Apple TN3178](https://developer.apple.com/documentation/technotes/tn3178-checking-for-and-resolving-build-uuid-problems), [electron-builder issue #9158](https://github.com/electron-userland/electron-builder/issues/9158).
Objavljen izvor
Preuzmi ZIP izvora
CH-J Server Manager
Pregledaj direktorije i datoteke za određeni programski izdanje.
CH-J / Server Manager
196 datoteke
core-20261013T133631Z-faa4ab45100e
Dodano: Datum nije zabilježen · Izgrađeno:
1
# macOS local network access3
CH-J Server Manager requests local network access when you connect to a local4
SSH server. Allow the macOS prompt. If access was denied, enable CH-J Server5
Manager in **System Settings → Privacy & Security → Local Network**, then6
connect again. The app cannot override this choice.8
## Packaging10
Electron ships prebuilt launchers with shared Mach-O UUIDs. macOS uses these11
UUIDs when identifying applications for local network access. `afterPack.js`12
therefore assigns application-specific UUIDs to the main launcher and Electron13
helper launchers **before signing**. The UUIDs include the bundle identity,14
launcher path, architecture and packaged `app.asar` digest. Repeating packaging15
of the same payload preserves its UUIDs; a different payload gets different16
UUIDs without changing the application version or bundle identifier.18
`packageMacInstaller.js` also prepares this identity when invoked directly,19
prefers an installed Developer ID Application identity over an ad-hoc signature,20
and checks the UUIDs, bundle ID, unchanged application version, local network21
usage description and code signature in the final mounted DMG. Without a22
Developer ID Application certificate it produces an ad-hoc test build. An Apple23
Development certificate is not a Developer ID distribution certificate.25
Only the small main/helper launchers are patched. Their original Electron dSYMs26
will no longer match; Electron Framework and its UUID/debugging symbols remain27
unchanged. Installed apps and older build copies are never modified by this28
packaging step.30
Run `npm run build:mac` to produce the corrected installer. Install that build31
and launch it from Finder to test local network access. A packaging smoke test32
or `npm start` inherits Terminal's network access and cannot verify the Finder33
permission prompt. Multiple installed copies can still confuse macOS permission34
settings; do not use a global privacy reset or disable system protections.36
References: [Apple TN3179](https://developer.apple.com/documentation/technotes/tn3179-understanding-local-network-privacy),37
[Apple TN3178](https://developer.apple.com/documentation/technotes/tn3178-checking-for-and-resolving-build-uuid-problems),38
[electron-builder issue #9158](https://github.com/electron-userland/electron-builder/issues/9158).SHA-256
da470ec29ca80143ac276444b87c82b2223b1ff0e05000dfe379f5de9a643ddcCH-J Proprietary Software License 1.14 · Izvor je osiguran pod CH-J Proprietary Software License 1.14. Njena dostupnost ne mijenja uvjete licenciranja niti daje dodatna prava.
Arhiv SHA-256
de757268dbc4f0226549f8b4f41f9b7e585c856ee97fa0d43b17a0e95c281449