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

Use URL encoding for binary values #69

Draft
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

saper
Copy link
Member

@saper saper commented Sep 28, 2024

If PKCS#11 URI format is desired, as proposed #4, let's tell our binary serialization routines to accept and generate %20 instead of \x20.

@saper saper marked this pull request as draft September 28, 2024 12:55
)) != CKR_OK
) {
goto cleanup;
}
Copy link
Member Author

@saper saper Sep 28, 2024

Choose a reason for hiding this comment

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

If we don't check the error code here, an unmodified "empty" target buffer will be returned in case _pkcs11h_util_binaryToHex fails. This could go into master anyway.

@dwmw2
Copy link

dwmw2 commented Sep 28, 2024

This is changing the legacy, serialisation format? Is there any need to do that? We should be using RFC7512 URIs by default and only accepting the legacy format for compatibility, surely? Changing the legacy format doesn't seem like it's going to help anything?

@saper
Copy link
Member Author

saper commented Sep 28, 2024

This is PR is the first step towards PKCS#11 URLs. It shouldn't be merged at this stage. I just try to see how much we can re-use the existing code.

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