Skip to content

ARTART: clarify PBES2 p2c rejection threshold (Section 3.13)#48

Closed
yaronf wants to merge 1 commit into
mainfrom
ys-artart-313
Closed

ARTART: clarify PBES2 p2c rejection threshold (Section 3.13)#48
yaronf wants to merge 1 commit into
mainfrom
ys-artart-313

Conversation

@yaronf

@yaronf yaronf commented Jul 13, 2026

Copy link
Copy Markdown
Collaborator

Summary

Addresses ARTART review comment #4 from @smyslov on Section 3.13 (Limit Hash Iteration Count).

The previous text had two RECOMMENDED clauses whose relationship was ambiguous: an upper limit on iterations vs. rejecting p2c values larger than "twice that figure" (unclear whether "that figure" meant the limit or the OWASP example).

This rewrite:

  • States that implementations should reject p2c values exceeding their configured upper limit
  • Uses the OWASP 600,000-iteration example to illustrate a reasonable limit choice (twice that figure = 1,200,000)
  • Adds -07 document history entry

Issues

Closes #45

Test plan

  • make builds successfully
  • Co-author review

Note

This PR is independent of #47 (Section 3.11). Both add a -07 history entry; these will need to be merged into a single entry when both land.

Made with Cursor

Tie rejection to the configured upper limit and explain that the OWASP
example illustrates a reasonable choice for that limit.

Co-authored-by: Cursor <cursoragent@cursor.com>
@yaronf

yaronf commented Jul 13, 2026

Copy link
Copy Markdown
Collaborator Author

Closing without merge. After author review, we prefer the original wording; see comment on #45.

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.

ARTART: Clarify PBES2 p2c rejection threshold in §3.13

1 participant