Skip to content
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

qubes-i3-sensible-terminal: use qrexec-client directly #9

Merged
merged 1 commit into from
Sep 19, 2020

Conversation

lczerner
Copy link
Contributor

Currently qvm-run is used to start a terminal in a vm. However this will
keep stdin/stdout connected depleting inter-VM shared memory which is
a limited resource (as pointed out by Marek Marczykowski-Górecki).

To avoid this use qrexec-client directly with "-e" option to avoid
connecting stdin/stdout.

This should be fine since a running vm is already required to be able to
use qubes-i3-sensible-terminal.

QubesOS/qubes-issues#5969
Signed-off-by: Lukas Czerner [email protected]

@lczerner lczerner force-pushed the fix_i3_sensible_terminal branch from 437586c to fd44e40 Compare August 27, 2020 10:37
Currently qvm-run is used to start a terminal in a vm. However this will
keep stdin/stdout connected depleting inter-VM shared memory which is
a limited resource (as pointed out by Marek Marczykowski-Górecki).

To avoid this, use qrexec-client directly with "-e" option to avoid
connecting stdin/stdout. Note that qvm-run does not support this option
at the moment, but it could be worked around by pointing stdin/stdout to
/dev/null. However using qrexec-cliend seems like a more efficient
solution in this case.

This should be fine since a running vm is already required to be able to
use qubes-i3-sensible-terminal.

QubesOS/qubes-issues#5969
Signed-off-by: Lukas Czerner <[email protected]>
@lczerner lczerner force-pushed the fix_i3_sensible_terminal branch from fd44e40 to fcbc05e Compare August 27, 2020 11:16
@lczerner
Copy link
Contributor Author

Ok, I give up :) My keys are not expired, I even updated it on the keyserver but it still says expired. No idea how to fix this.

@marmarek
Copy link
Member

Ok, I give up :) My keys are not expired, I even updated it on the keyserver but it still says expired. No idea how to fix this.

This particular one is about the copy of your key on github. But the one on the keyservers seems fine.

Copy link
Member

@marmarek marmarek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will break when used from within GUI domain (qrexec-client directly is available in dom0 only). I'll fix that in separate commit.

@marmarek marmarek merged commit f874ab6 into QubesOS:master Sep 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants