Skip to content

Commit

Permalink
Update chapter06.md
Browse files Browse the repository at this point in the history
  • Loading branch information
bigbrett authored Mar 18, 2024
1 parent 99d0207 commit 5a64bf8
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions wolfSSL/src/chapter06.md
Original file line number Diff line number Diff line change
Expand Up @@ -196,9 +196,9 @@ The Crypto callback framework in wolfSSL/wolfCrypt enables users to override the
The high level steps use crypto callbacks are:

1. Compile wolfSSL with crypto callback support
2. Register your callback and unique device ID (`devId`) with wolfCrypt
2. Register a callback and unique device ID (`devId`) with wolfCrypt
3. Pass the `devId` as an argument to a wolfCrypt API function
4. (TLS only): associate the `devId` with your WOLFSSL context
4. (TLS only): associate the `devId` with a WOLFSSL context


#### 1. Compile wolfSSL with crypto callback support
Expand Down Expand Up @@ -234,7 +234,7 @@ wc_InitCmac_ex
This is not an exhaustive list. Please refer to the wolfCrypt API documentation to see if a particular algorithm supports crypto callbacks.

#### 4. (TLS only): associate the devId with your WOLFSSL context
To enable use of your crypto callbacks when using TLS, you must supply the “devId” arguments on initialization of your `WOLFSSL_CTX` or `WOLFSSL` struct.
To enable use of a crypto callback when using TLS, you must supply the “devId” arguments on initialization of a `WOLFSSL_CTX` or `WOLFSSL` struct.
```
wolfSSL_CTX_SetDevId(ctx, devId);
wolfSSL_SetDevId(ssl, devId);
Expand Down

0 comments on commit 5a64bf8

Please sign in to comment.