Checklist
Is your feature request related to a problem? Please describe.
I'd like to be able to use client.meshtastic.org or client-test.meshtastic.org with our tcp proxy, but there is no TLS front-end available for the proxy. Could we document/integrate the home-assistant TLS server or nginx to provide the appropriate TLS front end to allow secure connections to the proxy? This is not a security issue or request, just a convenience one.
Describe the solution you'd like
Create a second TCP port that front-ends the meshtastic tcp proxy using either the home assistant core SSL keys, if present, or a self-signed key.
Describe alternatives you've considered
Running a local copy of client.meshtastic.org in a docker container with HSTS disabled.
Additional context
The current meshtastic proxy/front-end no longer works, it simply downloads a file, and it's ancient anyway. Why not rip out that code and just use whatever client we want?
Checklist
Is your feature request related to a problem? Please describe.
I'd like to be able to use client.meshtastic.org or client-test.meshtastic.org with our tcp proxy, but there is no TLS front-end available for the proxy. Could we document/integrate the home-assistant TLS server or nginx to provide the appropriate TLS front end to allow secure connections to the proxy? This is not a security issue or request, just a convenience one.
Describe the solution you'd like
Create a second TCP port that front-ends the meshtastic tcp proxy using either the home assistant core SSL keys, if present, or a self-signed key.
Describe alternatives you've considered
Running a local copy of client.meshtastic.org in a docker container with HSTS disabled.
Additional context
The current meshtastic proxy/front-end no longer works, it simply downloads a file, and it's ancient anyway. Why not rip out that code and just use whatever client we want?