Security notes
These security notes summarize signing, execution, network, isolation, and process-handling behavior.
Overview
| Topic | Details |
|---|---|
| Code signing (Windows) | Signed via Azure Code Signing — CN=Sennheiser electronic SE & Co. KG, L=Wedemark, S=Lower Saxony, C=DE |
| Code signing (macOS) | Signed with Apple identity Sennheiser electronic (XKNNU9WTL7), hardened runtime enabled, Apple-notarized |
| Execution level | asInvoker — The application always runs with the privileges of the logged-in user. No automatic elevation occurs. |
| Network exposure | The SASS backend binds exclusively to 127.0.0.1:8181. It is not accessible from any network interface. |
| Renderer isolation | The Electron renderer process has no direct access to Node.js or operating system APIs. All host access is mediated through a typed IPC bridge in the preload script. |
| Orphan process handling | On startup, SFU checks for a leftover SASS process from a previous session via a PID file and terminates it before starting a new one. |
