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

Documentation: Improve 'How is Qubes Different' description #1860

Closed
tasket opened this Issue Mar 21, 2016 · 3 comments

Comments

Projects
None yet
2 participants
@tasket

tasket commented Mar 21, 2016

I keep hearing (even from technical people) that Qubes is just a nice convenient packaging of Xen or other Linux/hypervisor combination. It would benefit Qubes' image to hone the Tour page by enhancing the section comparing Qubes to other VMs on other systems. More detail and emphasis should be given to the graphics and clipboard isolation , as well as other ITL-developed code that enhances security in ways that isn't reproducible by assembling the right packages and configuration options in a regular OS.

I used to refer people to Joanna's blog post 'How is Qubes OS different from...', but even when "trusted window manager" is mentioned, it is presented in terms of usability and not the added security of graphics isolation.

@andrewdavidwong andrewdavidwong added this to the Documentation/website milestone Mar 21, 2016

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Mar 21, 2016

Member

Sounds good to me. The Tour might not be the optimal place for a comprehensive explanation of how Qubes is different from everything else, since that aims to be simple and short, but we can certainly include the highlights there, then perhaps link to a dedicated page.

@rootkovska, @marmarek: Any specific technical points we should make sure to mention?

Member

andrewdavidwong commented Mar 21, 2016

Sounds good to me. The Tour might not be the optimal place for a comprehensive explanation of how Qubes is different from everything else, since that aims to be simple and short, but we can certainly include the highlights there, then perhaps link to a dedicated page.

@rootkovska, @marmarek: Any specific technical points we should make sure to mention?

@tasket

This comment has been minimized.

Show comment
Hide comment
@tasket

tasket Mar 21, 2016

I think a full sentence or two at that point in the Tour would be optimal; perhaps as its own paragraph because of its significance.

tasket commented Mar 21, 2016

I think a full sentence or two at that point in the Tour would be optimal; perhaps as its own paragraph because of its significance.

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Oct 20, 2016

Member

I updated the page for this a while back but forgot to close this issue from the commit message. If you still think further edits are required, please feel free to submit a PR, comment, or re-open.

Member

andrewdavidwong commented Oct 20, 2016

I updated the page for this a while back but forgot to close this issue from the commit message. If you still think further edits are required, please feel free to submit a PR, comment, or re-open.

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