improved docs related to the private key #20
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tinder-maxwellelliott
approved these changes
May 24, 2024
|
For the record, I just noticed that Keychain Assistant let you customize the key pair, and the default value is an RSA 2048 key 👍🏼 
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I struggled a little bit understanding what I should use in the arg
--private-key-pathwhile creating a provisioning profileI am used to let Keychain Assistant to create the key pair and the CSR 😄
So this pr aims to improve the docs regarding the priv key. Do you consider it is the right place to include this command example?
Also are you using the same command
openssl genrsa -out key.pem 2048? Or do you suggest another one.Thanks!