On Wed, Feb 22, 2017 at 12:32 PM, Chris Laprise <[email protected]> wrote:
> Since this is an update of his Qubes R2 report already in the HCL, I have > enough info to include it for R3.2. I have the CPU model (from the body of > Oleg's first message), the chipset model, graphics, etc. Okay, please do. I don't remember exactly what I've already revealed about this peace of [cansored] that doesn't support VT-d. =) Next time when I'll decide to spend 1-2k$ for a laptop I'll look closer to Qubes requirements - last time I just bought and found it's not what I need half year later when got time to switch to Qubes. (very nice that usb stick option is available out of the box). Got a look into 4.0 hardware requirement - found that I have to buy a laptop when when 4.0 will appear in downloads. The only things changed since last report - I probably got either end of life for my ssd drive after last full rewrite or tools unaware about SSD made it report so strange things to dumb UEFI, that it disabled the primary sata channel. (to get a clue I need to check both alternatives: *) boot into windows and try to check w/ proprietary software *) check it in some other PC that has no stupid EFI bios pretending to be clever when I don't want it to) > But I agree the report file itself should have included a bare minimum with > the CPU. I vote for an option to show HCL info in 2 or 3 variants by user option: 1) as it is now with all details 2) with minumum requirement: model name, cpu info, chipset info, bios version, built in video info - all w/o exact IDs, no other info 3) just CPU, motherboard, bios information. And also I think, that ability to send _anonymous_ data about all parts w/ user only confirmation required is good thing. When anonymising report I'd stress on the following: *) send via .onion service w/o full unique identificators (optionally use crypto via temporary created at install time keys (and deleted right after encryption finished)) *) send one by one each hardware detail w/ random timeout within 24-96 hours(not within one hour!) to a fully automated receiver at vendor site (continue if rebooted before sending finished) Zrubi noted 2) and 3) as mostly useless, IIUC . -- Bye.Olli. gpg --search-keys grey_olli , use key w/ fingerprint below: Key fingerprint = 9901 6808 768C 8B89 544C 9BE0 49F9 5A46 2B98 147E Blog keys (the blog is mostly in Russian): http://grey-olli.livejournal.com/tag/ -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CABunX6MucMOiwHNKezbDzHxwuTRxrbEAZ4eqWZ606yf0UY%2BfvA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
