New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test and document hooking TCP connection into qrexec using socat #2148

Open
andrewdavidwong opened this Issue Jul 4, 2016 · 4 comments

Comments

Projects
None yet
3 participants
@andrewdavidwong
Member

andrewdavidwong commented Jul 4, 2016

On 2016-07-03 11:29, Marek Marczykowski-Górecki wrote:

It should be easy to hook any TCP connection into qrexec using socat.

Something like this (untested):

source VM: launch this somewhere (/rw/config/rc.local?)

socat TCP-LISTEN:4444,fork EXEC:"qrexec-client-vm target-vm my-tcp-service"

target VM: /usr/local/etc/qubes-rpc/my-tcp-service (this is stored in /rw):

socat STDIO TCP:localhost:4444

dom0: /etc/qubes-rpc/policy/my-tcp-service

source-vm target-vm allow

@andrewdavidwong andrewdavidwong added this to the Documentation/website milestone Jul 4, 2016

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Jul 4, 2016

Member

(This could become a tool instead of just documentation steps.)

Member

andrewdavidwong commented Jul 4, 2016

(This could become a tool instead of just documentation steps.)

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Feb 15, 2018

Member

@Joeviocoe: Please consider submitting this as a PR to the appropriate repo. I'm afraid it'll be overlooked as just a comment with a link to a gist.

Member

andrewdavidwong commented Feb 15, 2018

@Joeviocoe: Please consider submitting this as a PR to the appropriate repo. I'm afraid it'll be overlooked as just a comment with a link to a gist.

@tlaurion

This comment has been minimized.

Show comment
Hide comment
@tlaurion

tlaurion Feb 18, 2018

Contributor

@Joeviocoe: It would be awesome if this could be merged into the Qubes Network Server project, instead of pushing files manually into qubes.

@Rudd-O made it in such way that the Firewall GUI supported an additional "from-" prepending addresses and ports. His code was applied for each machines that had assigned static ips, making a generalist solution, both interesting for UDP and TCP.

Contributor

tlaurion commented Feb 18, 2018

@Joeviocoe: It would be awesome if this could be merged into the Qubes Network Server project, instead of pushing files manually into qubes.

@Rudd-O made it in such way that the Firewall GUI supported an additional "from-" prepending addresses and ports. His code was applied for each machines that had assigned static ips, making a generalist solution, both interesting for UDP and TCP.

@marmarek marmarek referenced this issue in trezor/trezor-core May 5, 2018

Open

Device disconnects in Qubes OS #167

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment