a3da85bfda
This way it will work independently from where qrexec-policy tool will be called (in most cases - from a system service, as root). This is also very similar architecture to what we'll need when moving to GUI domain - there GUI part will also be separated from policy evaluation logic. QubesOS/qubes-issues#910
8 lignes
170 B
Desktop File
8 lignes
170 B
Desktop File
[Desktop Entry]
|
|
Name=Qubes Qrexec Policy agent
|
|
Comment=Agent for handling policy confirmation prompts
|
|
Icon=qubes
|
|
Exec=qrexec-policy-agent
|
|
Terminal=false
|
|
Type=Application
|