Releases: cloudfoundry/loggregator-release
Releases · cloudfoundry/loggregator-release
Loggregator 101.10
- Add strict application ID validation to TrafficController (CVE-2018-1268 CVE-2018-1269)
- Fixes packaging bug in v101.9
Loggregator 89.6
Changelog
- Fix goroutine leak caused by slow consumers in TrafficController (CVE-2018-1268 CVE-2018-1269)
Loggregator 101.9
Changelog
- Add strict application ID validation to TrafficController (CVE-2018-1268 CVE-2018-1269)
Loggregator 99.1
Changelog
- Add strict application ID validation to TrafficController (CVE-2018-1268 CVE-2018-1269)
Loggregator 96.1
Changelog
- Add strict application ID validation to TrafficController (CVE-2018-1268 CVE-2018-1269)
Loggregator 89.5
Changelog
- Add strict application ID validation to TrafficController (CVE-2018-1268 CVE-2018-1269)
Loggregator 102.1
Changelog
- Add maximum allowed streams to reverse log proxy (set with
reverse_log_proxy.egress.max_streams-- defaults to 500) - Fix race condition in doppler
- Metron agent populates sourceID if none is given
Loggregator 101.8
Changelog
Fix a race condition in doppler.
Loggregator 102.0
Changelog:
- break out metron agent as a separate release, the
Loggregator-Agent; still included as a submodule, so no breaking changes - update rlpreader to take in
--counterNameand--gaugeNamesflags - enable deterministic routing in RLP to consistently shard counter metrics
- fix bug in trafficcontroller's UAA secret so it handles special characters
- remove noisy doppler connection and disconnect logs in rlp; emit
log_router_disconnectscounter metric instead
Loggregator 101.6
Changelog:
- Change RLP health endpoint to default to random port.
- Metron health endpoint only listens on localhost
- Bump Go to 1.9.4
- Fix doppler emitting multiple ingress metrics.