-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
build and upload qubes-remote-support package #6364
Comments
Was there a security discussion about this somewhere? I'd like to read more of the context. This will be a sensitive topic for many users, who will want assurance that all remote functionality is strictly opt-in. Ideally, we'll be able to tell users that, unless they follow specific instructions to install qubes-remote-support, the code will not even be present on their systems, and hence that there will be no possibility of remote compromise through this functionality on a default Qubes installation. I'm guessing that's going to be the case, but I'd like to confirm. |
This one is easy:
|
Good to hear. Thanks! |
@marmarek the deadline for payout for that NlNet run is on April, after which money disappears. Can we prioritize this? |
X2go is currently broken due to upstream issue: ArcticaProject/nx-libs#1009. Fix was already proposed, but wasn't deployed yet. |
I would add release notes tag and R4.1 milestone, i think this is quite notable optional functionality now present in R4.1. |
Task for @marmarek. (As confirmed by @marmarek.)
qubes-remote-support
Background:
https://www.whonix.org/wiki/Dev/Qubes_Remote_Support
The text was updated successfully, but these errors were encountered: