Closed jonrau1 closed 1 year ago
There is a breaking change in openssl that probably is the source of this issue, if you use the SSL branch to install it should be fixed.
Hey, I have just pushed out the 0.9 release of taky, which has completely overhauled the certificate generation routine. Please let me know if this works for you!
@jonrau1 Any news on how things are going? If you aren't having any more issues, I'll close this.
Closing this -- no more info! Please feel free to re-open if needed!
Unsure if it is actually because of the OS version, but seems the only logical step to me. This behavior is the same for quickstart and for the regular extended deployment. It is the same whether I use root (pi, in my case) or setup another user.
Some OS Info. Running of a RPI 3B+ for what that matters. Setup is on local LAN on 10.0.0.0/16 space - Taky server set to the local address of 10.0.0.191
Following the quickstart instructions, I was able to get the certificate installed from 10.0.0.191:8000/JENNY.zip without any issue on a LineageOS 19.1 device (Android 13) running the official tak[.]gov 4.7.0.3 image
I am given a variety of errors, first invalid certificate and when I look into the ATAK server configuration I am prompted for a username and password. Is there supposed to be one?
Next time I try it I am told to check the truststore - that is an ATAK error as well - unsure of what to do with that.
Any suggestions on how to troubleshoot this?