Bug 208423
| Summary: | security/fastd: Switch fastd to HTTPS | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Jan Bramkamp <crest_maintainer> | ||||
| Component: | Individual Port(s) | Assignee: | Kurt Jaeger <pi> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Many People | CC: | crest_maintainer, pi | ||||
| Priority: | --- | Flags: | pi:
maintainer-feedback+
|
||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
The fastd master site offers HTTPS. The attached patch switch the security/fastd master site URL from http:// to https://. Looks like upstream stepped to 18 already and it seems to be an easy upgrade. Would you mind if this change is done as 18 ? Btw, testbuilds as 18 @work. testbuilds are fine on 11a, 10.3a, 10.3i, 9.3a. At the moment the fastd v18 release is identical with the main git repos master branch. This will change again in the future so it makes sense to keep the fastd-devel port around. For now users can stay on whichever port suits their usecase. I have patches to move the ports to fastd v18, but submitted the PRs for the move from HTTP to HTTPS first, because I didn't anticipate the delay to get the changes committed. Does it mean you approve v18 or... ? A commit references this bug: Author: pi Date: Fri Apr 29 20:08:33 UTC 2016 New revision: 414291 URL: https://svnweb.freebsd.org/changeset/ports/414291 Log: security/fastd: 17 -> 18 Changes: http://fastd.readthedocs.org/en/v18/releases/v18.html PR: 208423 Submitted by: Jan Bramkamp <crest_maintainer@rlwinm.de> Changes: head/security/fastd/Makefile head/security/fastd/distinfo I just assume that it means maintainer approval. Committed, thanks! |
Created attachment 168826 [details] patch to switch master site from HTTP to HTTPS The libuecc master site offers HTTPS. The attached patch switch the security/libuecc master site URL from http:// to https://.