Lines Matching full:wolfssl
11 from the command line. This works with OpenSSL, wolfSSL, BoringSSL or AWS-LC as
344 ## wolfSSL build
346 wolfSSL also supports ECH and can be used by curl, so here's how:
350 git clone https://github.com/wolfSSL/wolfssl
351 cd wolfssl
353 ./configure --prefix=$HOME/code/wolfssl/inst --enable-ech --enable-debug --enable-opensslextra
358 The install prefix (``inst``) in the above causes wolfSSL to be installed there
368 ./configure --with-wolfssl=$HOME/code/wolfssl/inst --enable-ech
372 There are some known issues with the ECH implementation in wolfSSL:
375 incorrectly. [HRR issue](https://github.com/wolfSSL/wolfssl/issues/6802).)
380 [middlebox compatibility issue](https://github.com/wolfSSL/wolfssl/issues/6774)
382 ### Code changes to support wolfSSL
387 `one.one.one.one` for wolfSSL. The latter works for both, so OK, we us that.
388 - There seems to be some difference in CA databases too - the wolfSSL version
395 - tweak to ``configure.ac`` to check if wolfSSL has ECH or not
396 - added code to ``lib/vtls/wolfssl.c`` mirroring what's done in the
398 - wolfSSL does not support ``--ech false`` or the ``--ech pn:`` command line
401 The lack of support for ``--ech false`` is because wolfSSL has decided to
403 a compile time choice for wolfSSL, but a runtime choice for OpenSSL or
478 and accessing and logging ``retry_configs``, it seems wolfSSL has neither.