Skip to content
New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom

GetClientTLSConfig and SetClientTLSConfig are not thread safe #601

Open
ghjm opened this issue Apr 22, 2022 · 0 comments
Open

GetClientTLSConfig and SetClientTLSConfig are not thread safe #601

ghjm opened this issue Apr 22, 2022 · 0 comments

Comments

@ghjm
Copy link
Contributor

ghjm commented Apr 22, 2022

When using Receptor as a library, you might want to make use of GetClientTLSConfig and SetClientTLSConfig. (This was unavoidable before ReceptorVerifyFunc was made public.) Unfortunately, these functions have non-lock-protected map accesses and as a result, are not thread-safe. This should be fixed or at least documented.
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ghjm @akus062381