-
Notifications
You must be signed in to change notification settings - Fork 96
Improve how generate_psa_constants handles compatibility aliases #115
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
Improve how generate_psa_constants handles compatibility aliases #115
Conversation
@gilles-peskine-arm Could you please rebase and retarget the development branch if these changes are still relevant and desired? |
I'm pretty sure this is still relevant. It got stalled because no one reviewed it. I can pick it up if someone's available to review it. |
I can review |
No indented semantic change.
Support continuation lines and remove comments.
e0fb66a
to
6c3e632
Compare
Rebased to current |
Rather than hard-coding a list of deprecated aliases, assume that anything that's deprecated is an alias or otherwise not desired.
This was renamed from PSA_ERROR_TAMPERING_DETECTED. Add a backward compatibility alias in case somebody was already using it.
6c3e632
to
1983512
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
CI failures were only API changes with deprecated aliases (that's ok) and random DTLS failures (unrelated to this PR). Ok to merge. |
Improve how generate_psa_constants handles compatibility aliases. Declare a missing alias
PSA_ERROR_TAMPERING_DETECTED
.Targeting the API branch because that's where the renamings have been happening.