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
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I use ssl socat server on a raspberry A who's only job is to provide device to VM
I could use the TCP input for this, but right now it does not allow for SSL
I think it's pretty bad to have a S2 secured network going clear text over the network and most likely wifi, so i belive this is pretty important for security
Describe the solution you'd like
Right now my client and server are looking like that
The goal would be to have the default right now stay the same, and a way to provide a cert and CA path to enable SSL.
Then this could be added in the Frontend on the other repo
Describe alternatives you've considered
Right now, i am keeping my ssl socat server, and re-bouncing it locally in clear-text like so:
rpi --- SSL Socat ---> VM --- Clear local Socat ---> Container
This work, but is a dirty hack with additional point of failure and latency
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I use ssl socat server on a raspberry A who's only job is to provide device to VM
I could use the TCP input for this, but right now it does not allow for SSL
I think it's pretty bad to have a S2 secured network going clear text over the network and most likely wifi, so i belive this is pretty important for security
Describe the solution you'd like
Right now my client and server are looking like that
but i can't replace the client with the TCP:// socket in zwave-js.
To do so, i think it could be possible to use https://nodejs.org/docs/latest-v17.x/api/tls.html instead of https://nodejs.org/docs/latest-v17.x/api/net.html when cert are provided.
Having never done any JS, https://riptutorial.com/node-js/example/19326/tls-socket--server-and-client doesn't sound to complicated.
The goal would be to have the default right now stay the same, and a way to provide a cert and CA path to enable SSL.
Then this could be added in the Frontend on the other repo
Describe alternatives you've considered
Right now, i am keeping my ssl socat server, and re-bouncing it locally in clear-text like so:
rpi --- SSL Socat ---> VM --- Clear local Socat ---> Container
This work, but is a dirty hack with additional point of failure and latency
Additional context
zwave-js/zwave-js-ui#2345
node-zwave-js/packages/serial/src/ZWaveSocket.ts
Line 17 in 966e51f
The text was updated successfully, but these errors were encountered: