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.

Sign up for GitHub

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

Jump to bottom

Feature request: add hardware information masking #7523

Closed
Che15ea opened this issue May 24, 2022 · 5 comments
Closed

Feature request: add hardware information masking #7523

Che15ea opened this issue May 24, 2022 · 5 comments
Labels
P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.

Comments

@Che15ea
Copy link

Che15ea commented May 24, 2022

The problem you're addressing (if any)

It is possible to view the the model and serial number of CPU, memory, disk, motherboard for software in VM, which is unnecessary and negative for privacy in most cases.

The solution you'd like

The problem can be solved by adding a hardware info masking and spoofing at dom0 or hypervisor(which is better). Some people may also need a switch button to turn the masking off for individual VM.
@Che15ea Che15ea added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. labels May 24, 2022
@tzwcfq
Copy link

tzwcfq commented May 24, 2022

See this issue #1142.

@andrewdavidwong
Copy link
Member

Duplicate of #1142.

@andrewdavidwong
Copy link
Member

This appears to be a duplicate of an existing issue. If so, please comment on the appropriate existing issue instead. If anyone believes this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.

@andrewdavidwong andrewdavidwong added the R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one. label May 24, 2022
@Che15ea
Copy link
Author

Che15ea commented Jun 30, 2022

Huh? It was not solved in that issue. I don't want the software that I am using to collect the model or serial number of my CPU/RAM/Net Adapter/Hard drive.
It's not unnecessary, Kick secure and Whonix have done that.

@andrewdavidwong
Copy link
Member

Huh? It was not solved in that issue.

This can still be a duplicate of that issue regardless of whether that issue was solved. Being a duplicate is about whether the issues are about the same bug, enhancement, or task, not about how the matter was resolved. This point is simply a matter of issue tracker administration and organization, not an evaluation of the substantive technical content of the ticket. For more info, see: https://www.qubes-os.org/doc/issue-tracking/

I don't want the software that I am using to collect the model or serial number of my CPU/RAM/Net Adapter/Hard drive.
It's not unnecessary, Kick secure and Whonix have done that.

If you wish to express your opinion about the decision that was made on #1142, please post it as a comment on that issue. We don't allow duplicate issues just for the purpose of expressing disagreement with or protesting developer decisions on existing issues.

@QubesOS QubesOS locked and limited conversation to collaborators Jul 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@andrewdavidwong @Che15ea @tzwcfq