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
Would be great if OVMS can support HTTPS end point by being to authenticate the server, as well as establish secure SSL (encrypted) channels to OVMS. I know that you an optional NGINX front end, but the problem is that communication between the NGINX and the OVMS backend is over HTTP, and thus unencrypted. We would like to up an "Inferencing Service" based on OVMS. where one of the requirements is being able to "maintain confidentiality of inferencing inputs". We use Gramine Shielded Containers to transform the standard OVMS docker image to one that can readily run within Intel SGX, and this preserve input confidentiality during execution. However, the service still cannot guarantee full confidentiality unless the endpoints are also secure. NGINX does not solve the problem. I am happy to discuss further if someone wants more information. Thanks!
The text was updated successfully, but these errors were encountered:
Would be great if OVMS can support HTTPS end point by being to authenticate the server, as well as establish secure SSL (encrypted) channels to OVMS. I know that you an optional NGINX front end, but the problem is that communication between the NGINX and the OVMS backend is over HTTP, and thus unencrypted. We would like to up an "Inferencing Service" based on OVMS. where one of the requirements is being able to "maintain confidentiality of inferencing inputs". We use Gramine Shielded Containers to transform the standard OVMS docker image to one that can readily run within Intel SGX, and this preserve input confidentiality during execution. However, the service still cannot guarantee full confidentiality unless the endpoints are also secure. NGINX does not solve the problem. I am happy to discuss further if someone wants more information. Thanks!
The text was updated successfully, but these errors were encountered: