Lines Matching full:wolfssl
12 WolfSSL or boringssl as the TLS provider, depending on how you build curl.
345 ## WolfSSL build
347 WolfSSL also supports ECH and can be used by curl, so here's how:
351 git clone https://github.com/wolfSSL/wolfssl
352 cd wolfssl
354 ./configure --prefix=$HOME/code/wolfssl/inst --enable-ech --enable-debug --enable-opensslextra
359 The install prefix (``inst``) in the above causes WolfSSL to be installed there
369 ./configure --with-wolfssl=$HOME/code/wolfssl/inst --enable-ech --enable-httpsrr
373 There are some known issues with the ECH implementation in WolfSSL:
376 incorrectly. [HRR issue](https://github.com/wolfSSL/wolfssl/issues/6802).)
381 [middlebox compatibility issue](https://github.com/wolfSSL/wolfssl/issues/6774)
383 ### Code changes to support WolfSSL
388 "one.one.one.one" for WolfSSL. The latter works for both, so OK, we'll change
390 - There seems to be some difference in CA databases too - the WolfSSL version
397 - tweak to ``configure.ac`` to check if WolfSSL has ECH or not
398 - added code to ``lib/vtls/wolfssl.c`` mirroring what's done in the
400 - WolfSSL does not support ``--ech false`` or the ``--ech pn:`` command line
403 The lack of support for ``--ech false`` is because wolfSSL has decided to
405 a compile time choice for wolfSSL, but a runtime choice for OpenSSL or
480 accessing and logging ``retry_configs``, it seems WolfSSL has neither.