taky
taky - A simple COT server for ATAK
Features (and anti-Features!)
- Should support multiple ATAK clients simultaneously! You can see them on the map!
- GeoChats are routed to appropriate groups / UIDs, unless broadcast!
- SSL support with optional client keys!
- Some design consideration for XML security!
- Actually somewhat decent CoT routing uses Marti for other items. If unspecified, packets are considered broadcast.
- A hacked up XML parser written by someone who barely understands XML!
- Advanced Pythonic implementation of CoT model, with only 5 hours of combined industry experience in implementing CoT technology!
- Server shuts down with only one Ctrl+C!
- Does not require root to run!
- Thread safety? Why would you need thread safety?
- Slightly less-than-broken Data Package Server
- Requires no SQlite / databases! (For now!)
Requirements
- Python 3.7 or greater
- lxml
- dateutil
- flask
This application was developed with Python 3.8, and tested with ATAK v4.2.0.4. It is slowly progressing towards a beta state, and should work for playing around.
But, really. Using this is for anything important is probably a very-bad-idea (TM).
Installation
Inside the taky folder, run
$ git clone https://github.com/tkuester/taky
$ cd taky
$ python3 setup.py install
Alternatively, you can use pip!
$ python3 -m pip install taky
Usage
$ taky -h
usage: taky [-h] [-l {debug,info,warning,error,critical}] [-c CFG_FILE] [--version]
Start the taky server
optional arguments:
-h, --help show this help message and exit
-l {debug,info,warning,error,critical}
Log verbosity
-c CFG_FILE Path to configuration file
--version show program's version number and exit
# Run taky on 0.0.0.0:8087
$ taky
# Run taky within the folder (ie: if you can't install it)
~/taky $ python3 -m taky
taky, if no configuration file is specified, will check the current directory
for taky.conf and then /etc/taky/taky.conf.
With no (or an empty) configuration file, taky will start a tcp server on
0.0.0.0. A sample configuration file is located in the project root.
Metadata
Release files for taky 0.5.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| taky-0.5.1.tar.gz | 20.6 kB | Without provenance | Details for taky-0.5.1.tar.gz |
Release files / taky-0.5.1.tar.gz
| Download URL | taky-0.5.1.tar.gz |
|---|---|
| Size | 20.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4737e116da71c6ee4d2d50449ddd0d30a1503242e8323d108b327036c5bf6e00
|
|
BLAKE2b-256 checksum How to use checksums |
48fbcb2ffc301ff9786c35b9a38131313d76542c55beb68701e175f5888fa930
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.22.0 setuptools/45.2.0 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.8.5
|
Security for taky 0.5.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.