Documentation on how to setup programs or appvms to open links files in DVMs?

[Stumpy]

Are there any documents that tell how to setup either individual
programs, or better, appvms to open links, files, etc in DVMs?
I would love to have the VM that I use for webmail to automatically open
links or files in the webmails in a DVM, preferably with a context menu
or something like that gives a choice of regular dvm or whonix dvm.

I found Micha Lee's page which covers this but perhaps parts of it are
qubes 3.2 centric and dont work quite the same on 4.0?
Perhaps there are some other .desktop examples out there or a 4.0 guide
on doing this?

Anyway.

I tried something like:
qvm-open-in-vm fedora-28-dvm https://startpage.com

and it worked, or the window popped up and I had to select fedora-28-dvm

I made a .desktop like instructed containing:
[Desktop Entry]
Encoding=UTF-8
Name=BrowserVM
Exec=qvm-open-in-vm fedora-28-dvm %u
Terminal=false
X-MultipleArgs=false
Type=Application
Categories=Network;WebBrowser;
MimeType=x-scheme-handler/unknown;x-scheme-handler/about;text/html;text/xml;application/xhtml+xml;application/xml;application/vnd.mozilla.xul+xml;application/rss+xml;application/rdf+xml;image/gif;image/jpeg;image/png;x-scheme-handler/http;x-scheme-handler/https;

but when I tried to use
xdg-settings set default-web-browser
./local/share/applications/browser_vm.desktop

it tells me:
xdg-settings: invalid application name
Try 'xdg-settings --help' for more information.


So. Am i doing something wrong in the .desktop or in using xdg-settings
and
is there a way to have it bypass the window that asks which target VM,
or at least pulls that target vm up (as I already specified which target
vm I wanted to send it to via qvm-open-in-vm fedora-28-dvm

[Ivan Mitev]

On 12/1/18 2:08 AM, Stumpy wrote:
> Are there any documents that tell how to setup either individual
> programs, or better, appvms to open links, files, etc in DVMs?
> I would love to have the VM that I use for webmail to automatically open
> links or files in the webmails in a DVM, preferably with a context menu
> or something like that gives a choice of regular dvm or whonix dvm.

There is :)

https://github.com/Qubes-Community/Contents/blob/master/docs/common-tasks/opening-urls-in-vms.md

Feel free to improve the doc if you find things that aren' clear.

> I found Micha Lee's page which covers this but perhaps parts of it are
> qubes 3.2 centric and dont work quite the same on 4.0?
> Perhaps there are some other .desktop examples out there or a 4.0 guide
> on doing this?
>
> Anyway.
>
> I tried something like:
> qvm-open-in-vm fedora-28-dvm https://startpage.com
>
> and it worked, or the window popped up and I had to select fedora-28-dvm
>
> I made a .desktop like instructed containing:
> [Desktop Entry]
> Encoding=UTF-8
> Name=BrowserVM
> Exec=qvm-open-in-vm fedora-28-dvm %u
> Terminal=false
> X-MultipleArgs=false
> Type=Application
> Categories=Network;WebBrowser;
> MimeType=x-scheme-handler/unknown;x-scheme-handler/about;text/html;text/xml;application/xhtml+xml;application/xml;application/vnd.mozilla.xul+xml;application/rss+xml;application/rdf+xml;image/gif;image/jpeg;image/png;x-scheme-handler/http;x-scheme-handler/https;
>
>
> but when I tried to use
> xdg-settings set default-web-browser
> ./local/share/applications/browser_vm.desktop
>
> it tells me:
> xdg-settings: invalid application name
> Try 'xdg-settings --help' for more information.

You shouldn't use the full path. This should work:

xdg-settings set default-web-browser browser_vm.desktop

> So. Am i doing something wrong in the .desktop or in using xdg-settings
> and
> is there a way to have it bypass the window that asks which target VM,
> or at least pulls that target vm up (as I already specified which target
> vm I wanted to send it to via qvm-open-in-vm fedora-28-dvm

Yes there is a way, you have to edit some dom0 RPC permissions to
reflect your setup (it's in the doc too).

Ivan

[Stumpy]

Wow, thats quite long, perferct! I will check it out? Is it listed on
the Qubes Docs page?

[Ivan Mitev]

The doc is not in the official docs - yet.

The Qubes Community project is supposed to be a "staging" area for docs
that may one day make it to the official docs. It's also a collection of
links and resources. More info at:

https://qubes-community.github.io/