Issue #19388 has been updated by matz (Yukihiro Matsumoto). The original intention of `SecurityError` was the errors from taint checks. So most usages of it are misused (including core implementation). But at the same time, I don't want to punish existing code by removing it. So we keep it for the foreseeable future. Adding deprecation flag may not be needed. Matz. ---------------------------------------- Feature #19388: Deprecate SecurityError https://bugs.ruby-lang.org/issues/19388#change-101727 * Author: jeremyevans0 (Jeremy Evans) * Status: Open * Priority: Normal ---------------------------------------- I think we should deprecate `SecurityError` in Ruby 3.3 and remove it in Ruby 3.4. I think we probably should have deprecated `SecurityError` when `$SAFE` was deprecated, but better late than never. I've submitted a pull request to deprecate it: https://github.com/ruby/ruby/pull/7193 -- https://bugs.ruby-lang.org/