ladybird/Base/etc/SystemServer.ini
Andreas Kling d0a708fda4 Base: Run ProtocolServer as a separate "protocol" user
This is probably not the final design we'll want for this, but for now
let's run the HTTP client code as a separate user to reduce exposure
for the standard "anon" user account.

Note that "protocol" is also added to the "lookup" group, in order to
allow ProtocolServer to contact LookupServer for DNS requests.
2020-01-11 13:07:32 +01:00

54 lines
832 B
INI

[TTYServer]
# NOTE: We don't start anything on tty0 since that's the "active" TTY while WindowServer is up.
Arguments=tty1
StdIO=/dev/tty1
Priority=high
[ProtocolServer]
Socket=/tmp/portal/protocol
SocketPermissions=660
Lazy=1
Priority=low
KeepAlive=1
User=protocol
[LookupServer]
Socket=/tmp/portal/lookup
SocketPermissions=660
Lazy=1
Priority=low
KeepAlive=1
User=lookup
[WindowServer]
Socket=/tmp/portal/window
Priority=high
KeepAlive=1
User=anon
[Clock.MenuApplet]
KeepAlive=1
User=anon
[CPUGraph.MenuApplet]
KeepAlive=1
User=anon
[Audio.MenuApplet]
KeepAlive=1
User=anon
[AudioServer]
Socket=/tmp/portal/audio
# TODO: we may want to start it lazily, but right now WindowServer connects to it immediately on startup
Priority=high
KeepAlive=1
User=anon
[Taskbar]
Priority=high
KeepAlive=1
User=anon
[Terminal]
User=anon