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

Do SPDM responder have the ability to identify incoming GET_CAPABILITY parameters are invalid? #369

Open
owen126315 opened this issue Sep 11, 2024 · 1 comment
Labels
question Further information is requested

Comments

@owen126315
Copy link

In my scenario, responder support GET_CHUNK and maximum data transfer size is 255 due to transport layer limitation. And then, a requester goes through GET_VERSION and try to send GET_CAPABILITY which without GET_CHUNK.

From responder perspective, it can predict it is likely to hit "ResponseTooLarge" error in upcoming responds (e.g. CERTIFICATE, CHALLENGE_AUTH, MEASUREMENT). Can responder early notify requester with error code that requester capabilities cannot fulfill upcoming transaction?

@steven-bellock steven-bellock added the question Further information is requested label Sep 11, 2024
@steven-bellock
Copy link
Contributor

Can responder early notify requester with error code that requester capabilities cannot fulfill upcoming transaction?

Yes, but there's not a good error code that conveys that information. Only one that really fits is Unspecified and that's not going to tell the Requester that it needs to support chunking. So you're probably better off waiting for the request and then using ResponseTooLarge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants