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.
Jan 18 2019
Oct 15 2018
Aug 21 2018
Aug 14 2018
Jun 10 2018
May 3 2018
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,
Mar 14 2018
Jan 11 2018
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.
Dec 22 2017
that is obsolete
Dec 19 2017
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.
Nov 22 2017
Oct 11 2017
Should we just add letsencrypt ?
Sep 14 2017
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.
Aug 21 2017
Listed repo is gone
closing this as invalid
Jul 25 2017
that was resolved
Jul 24 2017
@dmbaturin please check when you have time
Dec 23 2016
@EwaldvanGeffen do we still need this ?
Dec 14 2016
We will move Jenkins to new host soon
Nov 18 2016
Sep 14 2016
Thanks for pointing!
Aug 31 2016
Jul 14 2016
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?
Jul 13 2016
Jul 10 2016
I made a thing that'll generate for you the development VM I'm currently using: https://github.com/giandvd/vyos-dev-vm
Jul 3 2016
updated to latest stable
Jun 4 2016
What we need for certain, other than git and build-essential, assuming the base system is minimal install:
Jun 3 2016
Apr 13 2016
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.
Mar 29 2016
Mar 5 2016
I edited permissions on maniphest app and all registered users now can create tasks
i will check out how to limit editing of non-user owned tasks
now it´s ok
will take care