You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
After messing around with the RAK13800, RAK4631 and RAK19007 I came to the conclusion that I am not able to connect via HTTP to the Meshtastic device running the latest current stable version.
In the Discord community I was advised to connect my Android phone with the Meshtastic app to the network so I can use the TCP option in the app to connect to the device however the person making me aware of this option also mentioned it is just TCP and no TCP with SSL meaning it is all in plain text. Given the secure nature of some people their working space/network it might be usefull to have an option to select, in the device options, a self-signed client (or server if hosting the WebUI) certificate or to upload your own certificate from a custom or a public PKI and to upload private CA’s.
Like this you can not only connect via TCP with SSL but also use HTTPS if your hardware supports it.
The text was updated successfully, but these errors were encountered:
Platform
Cross-Platform
Description
Hi,
After messing around with the RAK13800, RAK4631 and RAK19007 I came to the conclusion that I am not able to connect via HTTP to the Meshtastic device running the latest current stable version.
In the Discord community I was advised to connect my Android phone with the Meshtastic app to the network so I can use the TCP option in the app to connect to the device however the person making me aware of this option also mentioned it is just TCP and no TCP with SSL meaning it is all in plain text. Given the secure nature of some people their working space/network it might be usefull to have an option to select, in the device options, a self-signed client (or server if hosting the WebUI) certificate or to upload your own certificate from a custom or a public PKI and to upload private CA’s.
Like this you can not only connect via TCP with SSL but also use HTTPS if your hardware supports it.
The text was updated successfully, but these errors were encountered: