Skip to content

Commit

Permalink
Add reference to gem security resources
Browse files Browse the repository at this point in the history
  • Loading branch information
bf4 committed Nov 12, 2013
1 parent 6951991 commit 744d570
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion publishing.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

However, this method of securing gems is not widely used. It requires a number
of manual steps on the part of the developer, and there is no well-established
Expand All @@ -123,3 +123,4 @@ in [IRC](irc://chat.freenode.net/#rubygems-trust). The goal is to improve (or
replace) the signing system so that it is easy for authors and transparent for
users.

See the [Resources](/resources) page for more information about gem signing.

0 comments on commit 744d570

Please sign in to comment.