Skip to content

Conversation

@anhu
Copy link
Member

@anhu anhu commented Nov 21, 2025

Fixes #7356

@anhu anhu requested a review from wolfSSL-Bot November 21, 2025 17:09
@anhu anhu self-assigned this Nov 21, 2025
@devin-ai-integration
Copy link
Contributor

🛟 Devin Lifeguard found 1 likely issues in this PR

  • pointer-null-check snippet: Add alg_bits != NULL to the condition (e.g., if (c != NULL && alg_bits != NULL) { ... }) before writing to *alg_bits.

@anhu
please take a look at the above issues which Devin flagged. Devin will not fix these issues automatically.

@anhu
Copy link
Member Author

anhu commented Nov 21, 2025

I'm a little weary about this one as I think we were not filling it in on purpose. It doesn't look like that was an accident.

ret = c->bits;
if (alg_bits != NULL)
*alg_bits = c->bits;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The algorithm bits is c->bits while what is returned by OpenSSL is the strength bits which may be less due to the cipher suite.
CCM_8 has a strength_bits of 64 and an algorithm bits of 128.
Integrity only cipher suites have 0 strength bits but hash length algorithm bits.

@dgarske dgarske assigned anhu and unassigned anhu Dec 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[OpenSSL compatibility]: 5.6.6 and/or v5.6.6-stable-564-g3129e29a1 do not fill int pointed to by 2nd argument to SSL_CIPHER_get_bits(sc, &bitsalg);

2 participants