Releases: 9seconds/mtg
v2.1.7
v1.0.12
v2.1.6
What's Changed
- More detail and secure service example by @AHOHNMYC in #258
- Support of Go 1.18 by @9seconds in #259
- Add AmbientCapabilities by @arch-btw in #261
- More elegant management of ip allowlists by @9seconds in #262
- Tags for ipblocklisted by @9seconds in #263
New Contributors
Full Changelog: v2.1.5...v2.1.6
v1.0.11
v2.1.5
What's Changed
- modified docker commands for ease of use by @themegabyte in #249
- Fix broken ip lists by @9seconds in #252
- More correct error if no addresses are found by @9seconds in #253
- Use cidrranger instead of patricia by @9seconds in #254
- Add iplist_size metric by @9seconds in #255
- Update golangci-lint to 1.44.2 by @9seconds in #256
New Contributors
- @themegabyte made their first contribution in #249
Full Changelog: v2.1.4...v2.1.5
v2.1.4
v2.1.3
This release made 2 major improvements:
- Support of whitelists
- Performance tuning
I hope, now mtg is on par with official proxy. Another important thing, is that tunning of tcp-buffer size makes no effect. An option is not removed but completely ignored.
What's Changed
- fix TolerateTimeSkewness not being passed by @boypt in #221
- fix ipv6 doh-ip by @boypt in #223
- fix git clone url by @dariubs in #224
- Whitelist support by @9seconds in #231
- Simplify sockopts by @9seconds in #230
- Golangcilint 1.43.0 by @9seconds in #232
New Contributors
Full Changelog: v2.1.2...v2.1.3
v2.1.2
This release slightly extends an interface of mtglib.Logger
, adds a new option AllowFallbackOnUnknownDC
and relevant configuration option allow-fallback-on-unknown-dc
.
This option defines how mtg should behave if client requests unknown DC. Each time when client establishes a connection to a proxy, it sends a number of DC that it wants to connect to. This DC defines a number of the cluster: media, messages, channels and so on. But sometimes clients may issue a number mtg knows nothing about. It may be due to the bugs (#208) or because new cluster is present but a version of mtg is old enough to know about it. Telegram works in a way that each cluster may server any request (latency is an issue though). So, if you want a media, you can ask for that from messages cluster and vice versa. You'll get a response but with poor performance.
This option defines if mtg should reject unknowns (default behaviour for running with config and inverse for simple-run) or choose any known DC for that.
What's Changed
- Fallback to another DC if given is unknown by @9seconds in #210
- Bump docker build timeout to 20 minutes by @9seconds in #211
- Fix windows build by @9seconds in #213
- Add new BindJSON method to a logger by @9seconds in #214
- Update Actions permissions by @9seconds in #215
- Add configuration option allow-fallback-on-unknown-dc by @9seconds in #216
- golangci-lint 1.42.1 by @9seconds in #217
Full Changelog: v2.1.1...v2.1.2