Skip to content

Question about custom asynchronous CRL io #10038

@croepha

Description

@croepha

Version

Any

Description

This is a general question, I’m willing to use any wolfssl version or configuration.

I just want to confirm that I’m understanding the CRL IO callback mechanism. The callback must synchronously fetch the CRL right? There is no way to return with value that tells the caller of the connect function call again after the CRL is downloaded? Similar to how when using non blocking IO, it will return a “want read” error code? There isn’t a similar or equivalent mechanism for CRL?

Thanks!

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions