Add link guide of how to cryptographically sign your RubyGem #66
Conversation
Per discussion on [rubygems-developers](https://groups.google.com/d/msg/rubygems-developers/5ISp7D2tCu4/jNqk2KQzSsEJ)
Per discussion on [rubygems-developers](https://groups.google.com/d/msg/rubygems-developers/5ISp7D2tCu4/jNqk2KQzSsEJ)
| @@ -112,7 +112,7 @@ gems](http://docs.rubygems.org/read/chapter/21) since version 0.8.11. This | |||
| signing works by using the `gem cert` command to create a key pair, and then | |||
| packaging signing data inside the gem itself. The `gem install` command | |||
| optionally lets you set a security policy, and you can verify the signing key | |||
| for a gem before you install it. | |||
| for a gem before you install it. | |||
bf4
Nov 12, 2013
Author
Contributor
sorry about the whitespace...
sorry about the whitespace...
Add link guide of how to cryptographically sign your RubyGem
|
Thanks! I fixed the whitespace, too. No big deal. If you'd like, feel free to submit a new page with the contents of your blog. |
|
(Sorry for the whitespace, doing this from the github gui). @drbrain gladly. A whole new page? Sure. Anything special to do re: adding to the index of pages, specifying order, cross-linking, etc.? Should it be called "security" and replace http://guides.rubygems.org/publishing/#gem_security (with a link) Should I add a link from the command reference as well? And add links from http://guides.rubygems.org/specification-reference/#cert_chain and I thought I saw a link to docs somewhere |
|
A whole new page covering and named Security sounds great. The only required links are to update the index and preceding and following pages. Add whatever other links you feel appropriate. As mentioned in #67, you'll need to make changes to specification-reference.md in rubygems/rubygems. This is also true of command-reference.md. If you include your tutorial, be sure to link back to your original article. |
Per discussion on rubygems-developers