diff options
| author | Nobuyoshi Nakada <nobu@ruby-lang.org> | 2025-07-03 15:44:24 +0900 |
|---|---|---|
| committer | Nobuyoshi Nakada <nobu@ruby-lang.org> | 2025-07-03 15:44:24 +0900 |
| commit | c31bfd5467fb95c814db656a2d1d01641e10031b (patch) | |
| tree | aef27f27979fbe91454ff63911280d6d152315fe | |
| parent | 5817e58a60354050cfa059ec8e89202b6e9598d4 (diff) | |
[DOC] Fix markup in security.rdoc
| -rw-r--r-- | doc/security.rdoc | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/security.rdoc b/doc/security.rdoc index e428036cf5..fb0e4a52da 100644 --- a/doc/security.rdoc +++ b/doc/security.rdoc @@ -37,7 +37,7 @@ programs for configuration and database persistence of Ruby object trees. Similar to +Marshal+, it is able to deserialize into arbitrary Ruby classes. For example, the following YAML data will create an +ERB+ object when -deserialized, using the `unsafe_load` method: +deserialized, using the +unsafe_load+ method: !ruby/object:ERB src: puts `uname` @@ -54,15 +54,15 @@ simply integers with names attached to them, so they are faster to look up in hashtables. Starting in version 2.2, most symbols can be garbage collected; these are -called <i>mortal</i> symbols. Most symbols you create (e.g. by calling +called _mortal_ symbols. Most symbols you create (e.g. by calling +to_sym+) are mortal. -<i>Immortal</i> symbols on the other hand will never be garbage collected. +_Immortal_ symbols on the other hand will never be garbage collected. They are created when modifying code: * defining a method (e.g. with +define_method+), * setting an instance variable (e.g. with +instance_variable_set+), * creating a variable or constant (e.g. with +const_set+) -C extensions that have not been updated and are still calling `SYM2ID` +C extensions that have not been updated and are still calling +SYM2ID+ will create immortal symbols. Bugs in 2.2.0: +send+ and +__send__+ also created immortal symbols, and calling methods with keyword arguments could also create some. @@ -136,4 +136,4 @@ expose to untrusted clients. When using DRb, try to avoid exposing it over the network if possible. If this isn't possible and you need to expose DRb to the world, you *must* configure an -appropriate security policy with <code>DRb::ACL</code>. +appropriate security policy with +DRb::ACL+. |