mirror of
https://github.com/warmcat/libwebsockets.git
synced 2025-03-23 00:00:06 +01:00
![]() It's already the case that leaving off the "tls_trust_store" member of the streamtype definition in the policy causes the streamtype to validate its tls connections via the OS trust store, usually a bundle OpenSSL has been configured to load at init automagically, but also literally the OS trust store in windows case. Add tests to confirm that. |
||
---|---|---|
.. | ||
minimal-secure-streams | ||
minimal-secure-streams-alexa | ||
minimal-secure-streams-avs | ||
minimal-secure-streams-client-tx | ||
minimal-secure-streams-cpp | ||
minimal-secure-streams-hugeurl | ||
minimal-secure-streams-metadata | ||
minimal-secure-streams-metrics-proxy | ||
minimal-secure-streams-perf | ||
minimal-secure-streams-policy2c | ||
minimal-secure-streams-post | ||
minimal-secure-streams-proxy | ||
minimal-secure-streams-seq | ||
minimal-secure-streams-server | ||
minimal-secure-streams-server-raw | ||
minimal-secure-streams-sigv4 | ||
minimal-secure-streams-smd | ||
minimal-secure-streams-staticpolicy | ||
minimal-secure-streams-testsfail | ||
README.md |
Secure Streams
Secure Streams is a client API that strictly decouples the policy for connections
from the payloads. The user code only deals with the stream type name and payloads,
a policy database set at lws_context
creation time decides all policy about the
connection, including the endpoint, tls CA, and even the wire protocol.
name | demonstrates |
---|---|
minimal-secure-streams | Minimal secure streams client / proxy example |
minimal-secure-streams-tx | Proxy used for client-tx test below |
minimal-secure-streams-client-tx | Secure streams client showing tx and rx |