doc: qusal proxy service requires configuration

Fixes: https://github.com/ben-grande/qusal/issues/61
This commit is contained in:
Ben Grande 2024-06-17 21:46:21 +02:00
parent 1a72665a40
commit 534db9655c
No known key found for this signature in database
GPG Key ID: 00C64E14F51F9E56
2 changed files with 6 additions and 2 deletions

View File

@ -46,5 +46,6 @@ The development qube `dev` can be used for:
without direct network connection, you can open port to the desired SSH or without direct network connection, you can open port to the desired SSH or
HTTP server. HTTP server.
As the qube has no netvm, configure the `qusal.ConnectTCP` service to allow As the `dev` qube has no netvm, configure the Qrexec policy to allow or ask
for it to communicate with a remote repository for example. calls to the `qusal.ConnectTCP` RPC service, so the qube can communicate with
a remote repository for example.

View File

@ -64,6 +64,9 @@ drivers. Check files/admin/firmware.txt.
_Default policy_: every call is denied. _Default policy_: every call is denied.
As every call is denied by default, you need to add rules to you Qrexec policy
for a call to occur. Some examples are represented below.
Qube `dev` can ask to connect to `github.com:22` from `disp-sys-net`: Qube `dev` can ask to connect to `github.com:22` from `disp-sys-net`:
```qrexecpolicy ```qrexecpolicy
qusal.ConnectTCP +github.com+22 dev @default ask target=disp-sys-net qusal.ConnectTCP +github.com+22 dev @default ask target=disp-sys-net