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

DispVM should be non-networked by default, or have a clear option to users to do so #1121

Open
mfc opened this Issue Aug 15, 2015 · 3 comments

Comments

Projects
None yet
4 participants
@mfc
Member

mfc commented Aug 15, 2015

DispVMs are meant to be used to open untrusted files. However if that file can exfiltrate information (such as the fact it was opened), that can be seen as a security failure in some use cases.

DispVMs should be non-networked by default, and/or there should an option change this default if desired.

@unman

This comment has been minimized.

Show comment
Hide comment
@unman

unman Aug 16, 2015

Member

Look at #862 for the rationale for the current position.
There is already an option to change the default in R3. Look in qubes manager on advanced tab for a VM, or use qvm-prefs.

Member

unman commented Aug 16, 2015

Look at #862 for the rationale for the current position.
There is already an option to change the default in R3. Look in qubes manager on advanced tab for a VM, or use qvm-prefs.

@mfc

This comment has been minimized.

Show comment
Hide comment
@mfc

mfc Aug 26, 2015

Member

ah I hadn't seen that option in Qubes manager Advanced tab, I was looking in global settings.

I feel like the use-cases for inherited-network DispVMs are fewer (...printing?) than the use-cases for no-network DispVMs (opening untrusted files), so I would still submit to that being the default, with users being able to change it in the particular VM's settings as desired.

Member

mfc commented Aug 26, 2015

ah I hadn't seen that option in Qubes manager Advanced tab, I was looking in global settings.

I feel like the use-cases for inherited-network DispVMs are fewer (...printing?) than the use-cases for no-network DispVMs (opening untrusted files), so I would still submit to that being the default, with users being able to change it in the particular VM's settings as desired.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Aug 26, 2015

Member

One note - this shouldn't affect starting web browser in DispVM (from KDE/Xfce menu), of course.

Member

marmarek commented Aug 26, 2015

One note - this shouldn't affect starting web browser in DispVM (from KDE/Xfce menu), of course.

@marmarek marmarek added this to the Release 3.1 milestone Sep 1, 2015

@marmarek marmarek modified the milestones: Release 3.2, Release 3.1 Feb 8, 2016

andrewdavidwong added a commit that referenced this issue May 31, 2016

@marmarek marmarek modified the milestones: Release 3.2, Release 4.0 Aug 5, 2016

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