Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation: wolfSSL_BN_CTX_get() note #8359

Closed
wants to merge 1 commit into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions README
Original file line number Diff line number Diff line change
Expand Up @@ -68,6 +68,9 @@ NO_OLD_SHA_NAMES. These names get mapped to the OpenSSL API for a single call
hash function. Instead the name WC_SHA, WC_SHA256, WC_SHA384 and WC_SHA512
should be used for the enum name.

Note 4)
The function wolfSSL_BN_CTX_get() returns a new WOLFSSL_BIGNUM object. The object is not cached against the WOLFSSL_BN_CTX and must be freed by the application. This behavior is not consistent with BN_CTX_get() in OpenSSL.

*** end Notes ***

# wolfSSL Release 5.7.6 (Dec 31, 2024)
Expand Down
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -74,6 +74,8 @@ macro `NO_OLD_SHA_NAMES`. These names get mapped to the OpenSSL API for a
single call hash function. Instead the name `WC_SHA`, `WC_SHA256`, `WC_SHA384` and
`WC_SHA512` should be used for the enum name.

### Note 4
The function wolfSSL_BN_CTX_get() returns a new WOLFSSL_BIGNUM object. The object is not cached against the WOLFSSL_BN_CTX and must be freed by the application. This behavior is not consistent with BN_CTX_get() in OpenSSL.

# wolfSSL Release 5.7.6 (Dec 31, 2024)

Expand Down
Loading