尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證製作者的介紹僅有上面的一句話。 更多詳情請閱讀儲存庫 README。 儲存庫 README ↗
正在載入完整 README。
檢視完整 README ↗Libwebsockets is a simple-to-use, MIT-license, pure C library providing client and server for http/1, http/2, http/3, websockets, webtransport, MQTT and other protocols in a security-minded, lightweight, configurable, scalable and flexible way. It's easy to build and cross-build via cmake and is suitable for tasks from embedded RTOS through mass cloud serving.
It supports a lot of lightweight ancilliary implementations for things like JSON, CBOR, JOSE, COSE, and supports OpenSSL and MbedTLS v2/3/4 out of the box for everything. It's very gregarious when it comes to event loop sharing, supporting libuv, libevent, libev, sdevent, glib and uloop, as well as custom event libs.
100+ independent minimal examples for various scenarios, CC0-licensed (public domain) for cut-and-paste, allow you to get started quickly.
There are a lot of READMEs on a variety of topics. Doxygen API docs
We do a huge amount of CI testing per push
V5.0 now available... please upgrade to this or preferably v5.0-stable or main, as there are many security fixes only available on v5.0-stable and main; pre-5.0 releases are effectively deprecated.
There's a continuous incremental security audit in place finding and fixing new problems all the time at the moment, it's not a sign the code is weak: it's a sign I am using frontier models to make it extremely strong.
Code is pushed to main-dev now, Sai runs on it, if it passes, it is auto-promoted to main. Therefore from now on main only contains sai-tested pushes.
** NEW features available on v5.0 **
| LWS version | Platform | Protocols | Default TLS |
|---|---|---|---|
| <= 4.5 | non-FreeRTOS | any | OpenSSL |
| <= 4.5 | FreeRTOS | any | mbedTLS |
| 5.0+ | Windows | any | schannel |
| 5.0+ | *nix | h1, h2 | OpenSSL |
| 5.0+ | *nix | quic/h3 | GnuTLS |
| 5.0+ | FreeRTOS | any | mbedTLS |
quic/h3 is enabled for build by default... necessitating GnuTLS instead of OpenSSL to make quic/h3 work.
| TLS Library | Server TLS | Client TLS | QUIC Transport (TLS 1.3) | WSS / HTTPS | MQTT over TLS | ALPN (HTTP/2) | DTLS (WebRTC) | Session Cache | JIT Trust | GenCrypto |
|---|---|---|---|---|---|---|---|---|---|---|
| GnuTLS | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes |
| OpenSSL | Yes | Yes | No* | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| LibreSSL | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes |
| AWS-LC | Yes | Yes |
* Note: 1) Upstream OpenSSL does not provide the necessary QUIC TLS API (SSL_set_quic_method) to act as a cryptographic engine for LWS's QUIC transport. If you need QUIC/HTTP3 support, we recommend using BoringSSL or GnuTLS.
* *Note: 2) openHiTLS does not provide the necessary QUIC TLS API *
-DLWS_WITH_DHT=1| Yes |
| Yes |
| Yes |
| Yes |
| Yes |
| No |
| Yes |
| BoringSSL | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes |
| wolfSSL | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes |
| mbedTLS | Yes | Yes | Needs patch | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| SChannel | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes |
| BearSSL | Yes | Yes | No | Yes | Yes | Yes | No | Yes | Yes | Yes |
| openHiTLS | Yes | Yes | No | Yes | Yes | Yes | Yes (not SRTP) | Yes | Yes | Yes |