On 22 February 2018 at 15:52, Jean-Philippe Ouellet <j...@vt.edu> wrote:
> > One possible solution would be to add a new type of Qubes RPC rule: > present > > the user with the most recently opened DispVM to use as a default (that > they > > can change before clicking OK). It might look something like this: > > > > /etc/qubes-rpc/policy/qubes.OpenURL: > > > > $anyvm $dispvm ask,reuse > > > > (I think this idea needs a bit more thought!) > > As to point 4 and the implementation of VM re-use, nothing additional > is necessary from the current qubes-rpc plumbing. > > Returning a name would be undesirable since the source VM should not > be able to specify a specific destination VM (indeed, ideally might > not even know the names of any other VMs on the system). Increasing > complexity of the policy evaluation logic is also undesirable, since > this should ideally be kept as simple as possible. > > A solution today might include a service like: > $ cat url-redirector.RemoteOpenSession > #!/bin/sh > > while read -r url; do > case "$url" in > http://*|\ > https://*|\ > ftp://*) > qubes-open "$url" > ;; > *) > echo "Invalid URL" >&2 > ;; > esac > done > > and be invoked from another VM with: > $ qrexec-client-vm '' url-redirector.RemoteOpenSession > > This allows the source VM to keep a handle to an anonymous destination > VM to open arbitrary links in the future, without any cooperation or > changes in dom0 or policy evaluation or anything. > This all looks sensible to me. Thanks for thinking about it! Cheers, Andrew -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To post to this group, send email to qubes-devel@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/CAAXZBWJAnDqdwMQ9tecqO_y_B2x5KMNEU9bUgvcpg4d8Vm78CA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
