aboutsummaryrefslogtreecommitdiffstats
path: root/lib/rubygems/security.rb
diff options
context:
space:
mode:
authorzzak <zzak@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2014-01-20 04:57:31 +0000
committerzzak <zzak@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2014-01-20 04:57:31 +0000
commitdff0aa5a536937db2606b870aad42c2caee60adb (patch)
tree8fdd94b9da6190f47d2ab75f1e191ca1a37bb7a5 /lib/rubygems/security.rb
parent5ecbe189af77c309845d662f26c0b2797bde2915 (diff)
downloadruby-dff0aa5a536937db2606b870aad42c2caee60adb.tar.gz
* lib/rubygems/version.rb: [DOC] Use gender-neutral pronouns [ci skip]
* lib/rubygems/security.rb: ditto git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44661 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Diffstat (limited to 'lib/rubygems/security.rb')
-rw-r--r--lib/rubygems/security.rb6
1 files changed, 3 insertions, 3 deletions
diff --git a/lib/rubygems/security.rb b/lib/rubygems/security.rb
index bfd6fd225b..8c5fb7d9f2 100644
--- a/lib/rubygems/security.rb
+++ b/lib/rubygems/security.rb
@@ -120,11 +120,11 @@ end
# * HighSecurity - Here's the bugger that got us into this mess.
# The HighSecurity policy is identical to the MediumSecurity policy,
# except that it does not allow unsigned gems. A malicious user
-# doesn't have a whole lot of options here; he can't modify the
-# package contents without invalidating the signature, and he can't
+# doesn't have a whole lot of options here; they can't modify the
+# package contents without invalidating the signature, and they can't
# modify or remove signature or the signing certificate chain, or
# RubyGems will simply refuse to install the package. Oh well, maybe
-# he'll have better luck causing problems for CPAN users instead :).
+# they'll have better luck causing problems for CPAN users instead :).
#
# The reason RubyGems refused to install your shiny new signed gem was because
# it was from an untrusted source. Well, your code is infallible (naturally),