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

Possible ambiguity in keyUsage table #208

Closed
srdavidson opened this issue Aug 2, 2023 · 1 comment
Closed

Possible ambiguity in keyUsage table #208

srdavidson opened this issue Aug 2, 2023 · 1 comment
Labels

Comments

@srdavidson
Copy link
Contributor

It has been pointed out that some of the language in the table of 7.1.2.3 (e) could be viewed as ambiguous.

For dual use, bit positions SHALL be set for digitalSignature and keyEncipherment and MAY be set for nonRepudiation and dataEncipherment.

For clarity, the intended reading is

For dual use, bit positions SHALL be set for digitalSignature, SHALL be set for keyEncipherment, MAY be set for nonRepudiation, and MAY be set for dataEncipherment.

(In other words, nonRepudiation and dataEncipherment are not treated as a unit).

Similar text exists in the other columns.

@srdavidson
Copy link
Contributor Author

See proposed text at srdavidson@63f5436

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

No branches or pull requests

1 participant