Summary
This is a beta release of 2.0 for open-testing purposes. It is NOT meant for production use however it is suitable for individual or small-scale hobbyist use.
In this version, we've begun redesigning the codebase to be more stable, modular and extensible than ever before. We began to experiment with the power of this new design by further extending the feature set with things like smart emergencies and repeated cots.
Installation
Want to be a tester? Fantastic, we'd love to have you! To get started please keep a couple of things in mind...
- Install python3.11
- this is a pre-release version so it must be installed from pypi as follows "pip install FreeTAKServer==0.2.0.17b0"
- this version will not work with the 0-touch install so installation and configuration will need to be done manually until we are prepared for the release.
New Features (including alpha changes)
-
Python3.11 Default: Starting with this version python 3.11 is the default supported version of python for use with FTS.
-
Deprecated Insecure TLS: Insecure versions of TLS have now been deprecated
-
Smart emergencies: SA capacity undermined by a flood of emergencies? We've introduced smart emergencies which allow you to set a radius within which emergencies are sent to users. e.g. (Bob and Alice both have emergencies Bob is 5km away from Charlie, and Alice is 3000km away from Charlie, given the smart emergency distance is 20km Charlie will receive only Bob's emergency)
-
Repeated COTs: Sick of having to re-broadcast essential situation information every time a new client connects? That's where repeated cots come in. Using the API you can now create a COT which, by default, is re-sent to any and all newly connected clients to ensure everyone is on the same page.
-
CRL Re-Generation: we now support manual regeneration of the CRL upon expiration.
Bug Fixes (including alpha)
- Fixed leaking SSL sockets!: After much debugging and community collaboration we believe we have finally fixed the errors with the SSL COT Service dying with a large number of connected clients over time. (this has been tested with artificial traffic generation but we need input from real users!)
- Fixed Emergency API Endpoint: with the introduction of smart emergencies the emergency API endpoint no longer worked and prevented the UI Connect page from displaying emergencies, this has now been fixed.
What's Changed
- 539 fix emergency end point by @naman108 in #541
- Add missing code by @naman108 in #544
- Add json schema impl by @naman108 in #545
- Refresh of Dockerfile by @hickey in #511
- 408 relocation of server runtime files by @naman108 in #420
- disallowed connections with insecure TLS protocols by @naman108 in #546
- linting fixes by @naman108 in #548
Full Changelog: v2.0.13a0...v2.0.17b0