feat: install Qusal TCP Proxy on updatevm's origin

Document qusal.ConnectTCP in dev's Access Control as it defaults to deny
and causes confusion to users why it doesn't work by default.  This is
an exception of the rule that a formula cannot document the RPC service
of another formula to avoid duplication.
This commit is contained in:
Ben Grande 2024-06-26 12:20:35 +02:00
parent c2fc4b524a
commit eb3a8ab324
No known key found for this signature in database
GPG key ID: 00C64E14F51F9E56
7 changed files with 81 additions and 0 deletions

View file

@ -0,0 +1,21 @@
#!/bin/sh
## SPDX-FileCopyrightText: 2024 Benjamin Grande M. S. <ben.grande.b@gmail.com>
##
## SPDX-License-Identifier: AGPL-3.0-or-later
set -eu
updatevm="$(qubes-prefs updatevm)"
updatevm_class="$(qvm-prefs "${updatevm}" klass)"
proxy_target=""
case "${updatevm_class}" in
StandaloneVM) proxy_target="${updatevm}";;
AppVM) proxy_target="$(qvm-prefs "${updatevm}" template)";;
DispVM)
proxy_target="$(qvm-prefs "$(qvm-prefs "${updatevm}" template)" template)"
;;
esac
if test -n "${proxy_target}"; then
echo "${proxy_target}"
fi