Apache Traffic Control 4.1.1 is available here:
--traffic_ops_insecure=<0|1>
optional option to traffic_ops_ort.pl__RANGE_DIRECTIVE__
override
SYNCDS
runs by default
insecure
option in traffic_ops_golang
in favor of "tls_config": { "InsecureSkipVerify": <bool> }
It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures.
The PGP signatures can be verified using PGP or GPG. First download the KEYS as well as the `ASC` signature file for the relevant distribution. Make sure you get these files from the main distribution directory, rather than from a mirror. Then verify the signatures using:
% pgpk -a KEYS % pgpv apache-trafficcontrol-4.1.0.tar.gz.asc
or% pgp -ka KEYS % pgp apache-trafficcontrol-4.1.0.tar.gz.asc
or% gpg --import KEYS % gpg --verify apache-trafficcontrol-4.1.0.tar.gz.asc apache-trafficcontrol-4.1.0.tar.gz
$ gpg --verify apache-trafficcontrol-4.1.0.tar.gz.asc apache-trafficcontrol-4.1.0.tar.gz
gpg: Signature made Tue Feb 11 09:38:30 2020 MST
gpg: using RSA key BF4A8D7307B8EEC7BFB4D8CB8A0712500C70C06E
gpg: Good signature from "Rawlin Peters (apache signing key) " [ultimate]
Additionally, you should verify the SHA signature on the files. A unix program called `sha` or `shasum` is included in many unix distributions. It is also available as part of GNU Textutils. An MD5 signature (deprecated) consists of 32 hex characters, and a SHA512 signature consists of 128 hex characters. Ensure your generated signature string matches the signature string published in the files above.
Apache Traffic Control 4.1.0 is available here:
__RANGE_DIRECTIVE__
directive
allow_ip6
profile parameter to include the IPv6 addresses of your Traffic Monitors,
otherwise they will fail to poll over IPv6 and consider those caches to be
unavailable over IPv6)
db/admin.pl
script has now been removed. Please use the
db/admin
binary instead.
atstccfg
.