Hi, I am trying to transfer a file downloaded in a browser qube to another qube, Which is Tinycore and another is BSD. They both have access to the internet (but no browser) so I am limited to wget or curl. But I can’t use them as this is protonvpn .ovpn config file. Is there some other way to transfer the file to those standalone qubes as they are without all the qubes integrations?
Hey, you may want to look at:
I hope that it will help you!
If it doesn’t, then you can still resort to using a usb flash drive.
Hi thanks, I can’t use a flash drive even as Tinycore doesnt have those tools also, I will install the qubes-firewall as I am using mirage and give that a go. As it is just a txt file I am wondering if I can’t just temp host it somewhere and the wget or curl it 
I am feeling stupid now as it should be an easy thing. 
hmm…
There are two packages: dpkg-deb.tcz and dpkg.tcz. on tinycore I wonder if they could convert some of the qubes deb packages into tinycore. 
In this situation I always create a file archive from the files supposed to transfer and then i mount this archive and because xen can forward block devices you can add this mounted archive to tinycore and extract the file which is shown as a block device
Can’t you simply do, in dom0:
qvm-run --pass-io <qube_src> 'cat file.tar.gz' | qvm-run --pass-io <qube_tgt> 'cat > file.tar.gz'
You can bypass the VPN on both sides using firewall rules,and the use something like ssh or syncthing for the file transfer. It is not straightforward if you do not have a good understanding of how networking works, and you may create leaks in the VPN.
The BSD qube does not support this.
Could you create a block device and attach it?
The simplest method would be to use netcat to transfer the files between
qubes. You can configure the firewall to pass traffic between the
browser qube and the other qubes. Both Tinycore and BS have netcat
installed, so you would only have to install it in the browser qube.
On the other hand, most qubes have socat installed, and you should be
able to use socat on the browser qube and netcat on the receiver side,
so that installation is not strictly necessary.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
Thanks everyone, I could not mount the block device it gives errors. I would like a future proof solution so I gave up on the external curl / wget. I would like to continue using mirage-fw and not the qubes sys-fw. The link Firewall — Qubes OS Documentation requires a terminal to sys-firewall. Could these be done with mirage? Otherwise I was thinking of some terminal friendly external ( or internal) file-server. I agree netcat / ssh or synthing would be a good way for future non-qubes friendly VM’s… Its a work in progress. But I am curious how others approach this issue, as I am sure I am not alone with this.
I use an offline firewall (named disposable) for this purpose, configured
to pass traffic between qubes. Keep one in reserve if you will want to
do this again.
I use netcat - it’s simple to use and allows traffic either way. You
could use a simple script to automate on the “normal” qubes side.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
2 Likes