mirror of
https://github.com/warmcat/libwebsockets.git
synced 2025-03-16 00:00:07 +01:00
![]() warmcat.com and libwebsockets.org use Let's Encrypt certificates... LE have changed their CA signing arrangements and after 2021-01-12 (the point I renewed the LE server certs and received one signed using the new arrangements) it's required to trust new root certs for the examples to connect to warmcat.com and libwebsockets.org. https://letsencrypt.org/2020/09/17/new-root-and-intermediates.html This updates the in-tree CA copies, the remote policies on warmcat.com have also been updated. Just goes to show for real client infrastructure, you need to run your own CA (that doesn't have to be trusted by anything outside the clients) where you can control the CA lifetime. |
||
---|---|---|
.. | ||
minimal-secure-streams | ||
minimal-secure-streams-alexa | ||
minimal-secure-streams-avs | ||
minimal-secure-streams-client-tx | ||
minimal-secure-streams-cpp | ||
minimal-secure-streams-metadata | ||
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 |