Qubes OS 4.2 Signed Weekly Builds

[adw]

@vaticanvoodoo

I am trying to test 4.2 on a librem 14 laptop, but have no access to post in the testing group, so while I want to contribute, I am not really able to. I’m been using qubes for a little over a year and I am a habitual alpha/beta tester so I’d be happy to help.

Thank you for contributing! Please have a look at the instructions for joining the testing team here:

Joining the Testing Team

What’s the testing team? It’s a group of users who help make Qubes better. They commit to testing updates and releases of Qubes OS, and are willing to provide test results, confirm issues, and identify particular edge cases. This is key to detecting issues early on, and stop them affecting more users. Who should join? Community members with demonstrated track-record of good quality contributions. What’s the risk? For those willing to enable the testing repositories for the current releas…

[deeplow]

@deeplow

@Insurgo

Where are Q4.2 testing reports and discussions? I am part of the testing team but I see no activity there. Maybe there is issues with my account? @deeplow ? No 4.2 testing category, just this post About the 4.2 Testing category ?

Unfortunately there hasn’t been too much activity there .

I’m not sure, but I proposed an idea here.

[Insurgo]

Note: next weekly builds will boot from ISO on next builds.

Last openqa build booted from Heads today, with user having to detach sign manually with his own key and having to validate integrity first manually.

This is why we love detached signatures after all: They do both in one step: validating integrity and authenticity at once.

Trace: Installer fails to boot from USB stick with with ISO file on it · Issue #8422 · QubesOS/qubes-issues · GitHub

[Insurgo]

Created an issue specific to installer related problem that cannot be resooved but by reinstalling Track installer related bugs and needed packages (templates versions including needed packages) · Issue #8449 · QubesOS/qubes-issues · GitHub

[quantum]

The latest weekly build, Qubes-4.2.202308260643-x86_64.iso, doesn’t recognize my AX201 WiFi card. And I don’t have access to a LAN to check a wired connection. fyi

[Insurgo]

@Insurgo

@Insurgo

I would love all of you to read Newly populated private volumes don’t get proper SELinux labels · Issue #8242 · QubesOS/qubes-issues · GitHub

Note that Qubes-4.2.202308270121-x86_64.iso forward should include the fix to use fedora templates for dispm sys-net.

Haven’t had the chance to fix it myself, but should be there. This iso+detached signature should boot from Heads.

Note the recent builds of Heads now support exfat by default. This means that if you bought a SD card or a USB thumb drive, you can download iso + iso.asc directly to that drive and boot from USB from Heads to test it directly without having to verify either integrity or authenticity of the ISO. Heads will take care of it (tested in prior weekly iso.)

@fepitre

ISOs are built like @marmarek said, in a dedicated build machine like how the official ones are done. They can be downloaded at Index of /qubes/iso-testing/

Happy testing!

[ymy]

switching sys-net to debian template fixed that for me.

[Insurgo]

@ymy

switching sys-net to debian template fixed that for me.

@Insurgo

I see last weekly iso is from 8 of august and we are the 23rd.
I was hoping to see core-agent-linux v4.2.19 (r4.2) · Issue #3940 · QubesOS/updates-status · GitHub fixed but commented at core-agent-linux v4.2.19 (r4.2) · Issue #3940 · QubesOS/updates-status · GitHub fixing Newly populated private volumes don’t get proper SELinux labels · Issue #8242 · QubesOS/qubes-issues · GitHub.

Point is that this mitigation should not be needed anymore from Qubes-4.2.202308270121-x86_64.iso on, including the latest rc3

[Qball]

https://qubes.notset.fr/iso-testing/

Torrents NOT working AGAIN. Stalled!

Please open a Tribler Channel or post on i2p. If you don’t check your torrents, I will try calling you names AGAIN… remember. You deserve it!

[DVM]

This is a personal repo, no obligation that anything works on it, that’s the whole point of “testing”.
If you want Qubes 4.2, download the torrent file from the official website.

Download Qubes OS

[Sven]

@Qball

I will try calling you names AGAIN… remember. You deserve it!

That would be a CoC violation with intent and announcement: instaban.

Ask nicely or do something to improve the situation yourself. Entitled foul mouths are not welcome and won’t be tolerated. This is an official warning.

[qc0]

Would it be possible @deeplow @marmarek for the Weekly Builds Signing Key to be signed by the (Ultimately trusted) Qubes Master Signing Key? Or any other key connected to the Qubes project?

Now that Testing new releases and updates | Qubes OS is recommended on the Qubes website, this would encourage good security practices around distrusting the infrastructure. Esp. since qubes.notset.fr distributes both the .iso files and the signing .key, and doesn’t even use HTTPS

Thank you!

[apparatus]

@qc0

Esp. since qubes.notset.fr distributes both the .iso files and the signing .key, and doesn’t even use HTTPS

It has https support.

[gonzalo-bulnes]

@apparatus

It has https support.

@qc0 I can confirm this. The redirection is not automatic on the first visit, but if you ask for HTTPS, you get it: https://qubes.notset.fr/

And HSTS is enabled, so your browser should upgrade to HTTPS automatically on subsequent visits. (source)

Note that I don’t think any of this makes your point moot! (Even if I suspect that the solution you propose may not be practical, but I’ll let folks who know, rather than suppose answer that.)

[unman]

Would it be possible @deeplow @marmarek for the Weekly Builds Signing Key to be signed by the (Ultimately trusted) Qubes Master Signing Key? Or any other key connected to the Qubes project?

By the QMSK? No. They are images built outwith the build infrastructure
AFAIK. fepitre has been clear about the build infrastructure and risks.
They are , however, signed by fepitre-bot.

Esp. since qubes.notset.fr distributes both the .iso files and the signing .key, and doesn’t even use HTTPS

It does use HTTPS

[qc0]

okay, thank you for the thoughtful replies! FYI @fepitre the current weekly build key is not signed by fepitre-bot (the previous weekly key is, however).

clarifying the risks in the top post I think would be helpful, as would making the signing key (or its fingerprint) available on github.

cheers,

-qc

[Qball]

Mister Sven,
The way I look at it!
If the torrents are working I can have a test machine in 2 hours that includes test VMs and template (maybe hundreds of testers).
If Ferpitre has a Tribler channel or i2p pool, I can have a test machine in 1 hour because I can subscribe and run those networks.(maybe more than 1000 testers)
If I have to download 4-5 hours… I’m out! Same with building from scratch.
As master Yoda said: Enqule do or not do don’t send me on some road to Katin or Arheim like the brave Polak army. With sugar on top: Don’t f with good things.

[DVM]

You are talking about an unofficial repo. The official Qubes website offers a torrent file with seeders. You are being aggressive for no reason at all.

[gonzalo-bulnes]

@Qball

You are threading a fine line.

You’ve made clear that you would find convenient if other people made things convenient for you. Everybody gets that, who wouldn’t.

You are not entitled to anyone’s work, though. By participating in this forum, however, you agree to follow some rules. You’ve been reminded of the rules and given an official warning.

I know you know that everybody can make mistakes, and what’s important is to get past them. With that in mind, the right time to let go and bring the tone down is now, so we can all keep enjoying the conversation.