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

TLS default config is never freed #39

Closed
ghost opened this issue Jul 19, 2015 · 0 comments
Closed

TLS default config is never freed #39

ghost opened this issue Jul 19, 2015 · 0 comments

Comments

@ghost
Copy link

ghost commented Jul 19, 2015

I think the TLS API default configuration is never freed. Also I don't see how the user can access the default configuration in order to have control upon it.

tls_free is related to the context. I think if there is tls_init, there should be tls_free which frees the global config allocated and other things global. But tls_free is related to the context, thus, its name should be like tls_ctx_free().. for me is confusing. In general I think API funcitons related to the context to have name like tls_ctx_...

Also I think the pointer arguments like ctx and others of the api functions should be checked if they were provided by the user as NULL, thus it will make the use of API functions more secure.

@ghost ghost closed this as completed Jul 19, 2015
This issue was closed.
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

No branches or pull requests

0 participants