core-admin/linux/system-config/qrexec-policy-agent.desktop

[Desktop Entry]
Name=Qubes Qrexec Policy agent
Comment=Agent for handling policy confirmation prompts
Icon=qubes
Exec=qrexec-policy-agent
Terminal=false
Type=Application
qubespolicy: run GUI code inside user session and expose it as dbus object 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 2017-04-06 15:39:31 +02:00			`[Desktop Entry]`
			`Name=Qubes Qrexec Policy agent`
			`Comment=Agent for handling policy confirmation prompts`
			`Icon=qubes`
			`Exec=qrexec-policy-agent`
			`Terminal=false`
			`Type=Application`