Skip to content

Updated email to facts@wolfssl.com#10787

Open
stenslae wants to merge 1 commit into
wolfSSL:masterfrom
stenslae:update-wolfssl-email
Open

Updated email to facts@wolfssl.com#10787
stenslae wants to merge 1 commit into
wolfSSL:masterfrom
stenslae:update-wolfssl-email

Conversation

@stenslae

Copy link
Copy Markdown
Member

Description

Changed info@wolfssl.com to the live email, facts@wolfssl.com. Renewed certs to match.

@stenslae stenslae self-assigned this Jun 25, 2026
@stenslae stenslae force-pushed the update-wolfssl-email branch from 44dec29 to dad1e95 Compare June 25, 2026 21:57

@wolfSSL-Fenrir-bot wolfSSL-Fenrir-bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Fenrir Automated Review — PR #10787

Scan targets checked: wolfcrypt-bugs, wolfcrypt-port-bugs, wolfcrypt-src, wolfssl-bugs, wolfssl-src
Findings: 1

High (1)

GEN_EMAIL test input array not updated to match new expected string

File: tests/api.c:20575
Function: test_wolfSSL_GENERAL_NAME_print
Category: Copy-paste errors

The email[] input array still encodes "info@wolfssl.com" while emailStr was changed to "email:facts@wolfssl.com". The GEN_EMAIL case prints "email:info@wolfssl.com", so the XSTRNCMP assertion at line 20751 returns nonzero and the test fails in OPENSSL_ALL builds.

Recommendation: Change the email[] array bytes to spell "facts@wolfssl.com" so the constructed GEN_EMAIL matches emailStr.

Referenced code: tests/api.c:20575-20579 (5 lines)


This review was generated automatically by Fenrir. Findings are non-blocking.

@stenslae stenslae force-pushed the update-wolfssl-email branch from dad1e95 to d26ca4b Compare June 25, 2026 22:05
@stenslae stenslae force-pushed the update-wolfssl-email branch from d26ca4b to 464df88 Compare June 25, 2026 22:08
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.

2 participants