Skip to content

API specifications at version 1.0 beta1 #38

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

Conversation

gilles-peskine-arm
Copy link
Collaborator

Upload the generated PDF and HTML for the PSA Crypto API 1.0 beta1.

Documentation generated from the PSA Crypto API documentation private
repository at tag "psa-crypto-api-1.0-beta1".

This uses some of the files include/psa/crypto*.h from the mbed-crypto
repository at tag "psa-api-1.0-beta".
@gilles-peskine-arm gilles-peskine-arm added enhancement New feature or request needs: review The pull request is ready for review. This generally means that it has no known issues. labels Jan 31, 2019
Copy link
Contributor

@Patater Patater left a comment

Choose a reason for hiding this comment

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

  • Pre-existing issue observation: psa_generate_key_extra_rsa still shows up as a "Class", and it's the only "Class". Any idea why or how to fix this?
  • Mild protest: Is this meant to be generated from the headers we shipped in the 1.0b1 or the currently checked in version? I think I'd prefer the docs to match the implementation at all times, but we need a web presence with the spec ASAP, so this'll do.
  • Pre-existing issue observation: some of the group__crypto__types.html don't have Doxygen documentation.

@gilles-peskine-arm
Copy link
Collaborator Author

Regarding the Doxygen issues: this will be fixed in the spec after migrating to the new format. For the implementation, I don't know how to fix it.

The text says that it's linking to the specification. That's why it's pointing to a different branch. Later we'll make a process to have the library documentation on tls.mbed.org or crypto.mbed.org or whatever.

Copy link
Contributor

@dgreen-arm dgreen-arm left a comment

Choose a reason for hiding this comment

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

Other than the comments already mentioned, looks fine to me.

@Patater Patater added the needs: work The pull request needs rework before it can be merged. label Feb 5, 2019
@Patater
Copy link
Contributor

Patater commented Feb 5, 2019

This is not quite passing CI... there are some failures in all.sh

@Patater Patater added needs: ci Needs a passing full CI run and removed needs: review The pull request is ready for review. This generally means that it has no known issues. labels Feb 5, 2019
@gilles-peskine-arm
Copy link
Collaborator Author

Failures are expected since the code hasn't caught up with the specification. That's why this is for the psa-crypto-api branch and not for development.

@Patater
Copy link
Contributor

Patater commented Feb 5, 2019

OK, didn't catch that this was for non-development branch. Mergin'.

@Patater Patater removed needs: ci Needs a passing full CI run needs: work The pull request needs rework before it can be merged. labels Feb 5, 2019
@Patater Patater merged commit 2f74f33 into ARMmbed:psa-crypto-api Feb 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants