Skip to content
This repository was archived by the owner on Feb 1, 2024. It is now read-only.

Clarifying Signature Policy selection #1578

Merged
merged 1 commit into from
May 8, 2018

Conversation

ruffsl
Copy link
Contributor

@ruffsl ruffsl commented Apr 17, 2018

when submitting a Development Services Access Request to Intel.

Copy link
Contributor

@askmish askmish left a comment

Choose a reason for hiding this comment

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

Hi ruffsl, Thanks for your contribution. For commit message we follow the rules in the contributor guide here: https://sawtooth.hyperledger.org/docs/core/releases/latest/community/contributing.html and this: https://chris.beams.io/posts/git-commit/#seven-rules
Could you update your commit messages and add a dco sign off as well.

@@ -153,7 +153,8 @@ Instructions for creating your own service provider certificate can be found
After your certificate is created you'll need to register it with the
attestation service.
`Click here <https://software.intel.com/formfill/sgx-onboarding>`_ for the
registration form.
registration form. Remeber to select ``Linkable`` when choosing the Attestation policy given that PoET relyes on "Linkable" EPID signatures. This means the device will always present a consistent identity within the Attestation service. Further details on Signature Policy can be found
Copy link
Contributor

Choose a reason for hiding this comment

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

"relies" is misspelled as "relyes"

Copy link
Contributor

Choose a reason for hiding this comment

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

"Remember" is misspelled as "Remeber".

Copy link
Contributor

Choose a reason for hiding this comment

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

Suggestion: "Please select Linkable option when" would read better in lieu of "Remember to select Linkable when"

Copy link
Contributor

Choose a reason for hiding this comment

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

"since" would be a better alternative for the "given that" in the text

@askmish askmish requested review from rbuysse and annechenette April 18, 2018 15:59
@ruffsl ruffsl force-pushed the patch-1 branch 2 times, most recently from 3ed3138 to 60411b4 Compare April 18, 2018 18:34
@ruffsl
Copy link
Contributor Author

ruffsl commented Apr 18, 2018

@askmish please let me know if more changes are needed.

@dcmiddle
Copy link
Contributor

dcmiddle commented Apr 23, 2018

@ruffsl looks good. Could you please just rebase the commit? We had some CI changes and this won't pass until your branch lays ontop of those changes. Will be something like...

git checkout this-branch 
git fetch upstream master
git rebase -i upstream/master
git push --force your-fork this-branch

@dcmiddle dcmiddle self-requested a review April 23, 2018 18:39
Selection of Signature Policy during submission of a Development
Services Access Request should be clarified to ensure users chose
the Linkable quote option, as it is necessary since PoET relies on
Linkable EPID signatures.

Signed-off-by: ruffsl <[email protected]>
@ruffsl
Copy link
Contributor Author

ruffsl commented Apr 23, 2018

@dcmiddle , thanks for the instructions. PR branch now rebased on to upstream master.

@peterschwarz peterschwarz requested a review from askmish April 24, 2018 15:52
@askmish askmish merged commit 00255c4 into hyperledger-archives:master May 8, 2018
@rberg2
Copy link
Contributor

rberg2 commented May 8, 2018

Hello, it looks like this commit introduced an error in the build system.
Take a look at this for sphinx issue for suggestions on how to prevent that from happening.
sphinx-doc/sphinx#3921

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

Successfully merging this pull request may close these issues.

4 participants