Skip to content

Commit c5c0e96

Browse files
Address review comments: expand PK acronym and add configure example
Co-Authored-By: Anthony H <[email protected]>
1 parent 3d5ab99 commit c5c0e96

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

wolfSSL/src/chapter06.md

+6-2
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ To use Atomic Record Layer callbacks, wolfSSL needs to be compiled using the `--
105105
106106
## Public Key Callbacks
107107
108-
wolfSSL provides Public Key callbacks for users who wish to have more control over DH, ECC, Ed25519, X25519, Ed448, X448, and RSA operations during the SSL/TLS connection.
108+
wolfSSL provides Public Key (PK) callbacks for users who wish to have more control over DH, ECC, Ed25519, X25519, Ed448, X448, and RSA operations during the SSL/TLS connection.
109109
110110
### DH Callbacks
111111
@@ -137,7 +137,11 @@ The user can set a context per WOLFSSL object (session) with `wolfSSL_SetDhAgree
137137

138138
Example callbacks can be found in `wolfssl/test.h`, under `myDhCallback()`. Usage can be seen in the wolfSSL example client.
139139

140-
To use DH callbacks, wolfSSL needs to be compiled with `HAVE_PK_CALLBACKS` and `HAVE_DH` defined.
140+
To use DH callbacks, wolfSSL needs to be compiled with `HAVE_PK_CALLBACKS` and `HAVE_DH` defined. This can be done using the configure option:
141+
142+
```sh
143+
./configure --enable-pkcallbacks
144+
```
141145

142146
### Ed25519 Callbacks
143147

0 commit comments

Comments
 (0)