On 10/28/2016 01:48 PM, HW42 wrote:
> Marek Marczykowski-Górecki:
> [...]
> > I see. The server part is much more critical, so it's ok to have as it
> > is now. Actually my solution also pass the data manually on the
> client side
> > - but it uses "cat" for this:
>
> > (echo $GIT_EXT_SERVICE $2 $3; exec cat) | qrexec-client-vm
> $VMNAME local.Git
>
> This unfortunately does not work if the remote simply exits. The problem
> ist that cat does not detect that it's output fd is closed and therefore
> still waits for input on stdin (You can observe this for example if you
> try to fetch from an non existing repo).
>
> That's the same reason why
>
> cat | /bin/true
>
> blocks. While you can work around it I'm not aware of a _simple_ trick
> to do it.
>
> What do you think of providing some way to pass a first line in
> qrexec-client-vm or some wrapper. Then not everybody who implements such
> simple qrexec services needs to implement their own "copier" and think
> of all the corner cases.
FWIW: This is exactly the issue that motivated me to create a solution
based on data copying — not being able to detect whether the remote
process had exited.
--
Rudd-O
http://rudd-o.com/
--
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-devel/4878102d-7e3a-c67d-5580-fc8182bf4e14%40rudd-o.com.
For more options, visit https://groups.google.com/d/optout.
