I didn't notice that this was still open, I can confirm the HTTPS method works as expected from VyOS 1.1.8 and later.

Why not "repairing" the master branch by first deleting its content in one commit and the merging current into master?

Just tested it on hvinfo and it seems to work as expected. The change is in the jenkins script,

The downloads.vyos.io is now using mandatory HTTPS. On the dev.packages.vyos.net, HTTPS is optional. To declare this closed, we need someone to independently verify that ISO build works with HTTPS for them.

that is obsolete

Awesome. :) Let me know if you ever need an extra pair of hands on the infrastructure front.

It will be sooner or later ;)

That's true, I would use a TLS mirror with a SHA-256 hash from the master. But I'd also want the master to be TLS.

If you can at least get a strong hash sum of the ISO from the master, that should be sufficient regardless of where the binary is downloaded from. Of course, if the master is compromised, all bets are off.

We should probably put in the mirror documentation that new mirrors must support TLS and existing mirrors are strongly urged to add support for TLS. However, to be clear, wanting a secure source for my downloads, I won't download from a mirror, because there's a lower level of trust. In fact, given a mirror with TLS and a the master source without TLS, I would chose the master source every time.

This begs the question about the mirror mechanism. My mirror supports TLS, but most don't.

In T422#8426, @syncer wrote:

Should we just add letsencrypt ?

Should we just add letsencrypt ?

The current implementation with postfix aliases is/was a bit problematic because all spam sent to it is forwarded to all members, and the mail servers where member addresses are get upset with mine and report me to spam lists.

Listed repo is gone
closing this as invalid

that was resolved

@dmbaturin please check when you have time

@EwaldvanGeffen do we still need this ?

We will move Jenkins to new host soon

@hexes fixed!
Thanks for pointing!

@dmbaturin can you check
https://github.com/giandvd/vyos-dev-vm
can we put this maybe under contrib or etc like with management library

I will install it,
maybe is better to sync wiki and docs from same source(instead of sync from wiki)?
not sure if something like that exists in nature, but possible there such systems?

I made a thing that'll generate for you the development VM I'm currently using: https://github.com/giandvd/vyos-dev-vm

updated to latest stable

What we need for certain, other than git and build-essential, assuming the base system is minimal install:

I can create Projects as @EwaldvanGeffen proposed
Tickets always created with need triage state
someone need to specify project tags and priority

I think questions and tasks are not convertible.

Can you make new tasks be assigned into some group 'triage' as for questions now is. The groups for questions should be kept simple as NAT, PBR, WLB, OPENVPN, IPSEC, DRIVER, KERNEL, ... because users will mostly interact with this part.