byroot (Jean Boussier) wrote in #note-2: > This is all from bundler / rubygems, so I believe we should close as a third party issue. Please note that was a filtered list, there are other dependecies, such as `pop3`/`imap`, `cgi`, and...pvalena (Pavel Valena)
Similarly to https://bugs.ruby-lang.org/issues/18272 ## Context When working on a new version of RHEL (with Ruby 3.0), the requirement is to have a better security (remove unsafe digests or limit the use for non-security purposes). T...pvalena (Pavel Valena)
Another suggestion from our internal discussion: ``` SHA1 should work for you, though it would be better if you could switch to EVP API from old SHA* API, if you by chance still use it. ```pvalena (Pavel Valena)
## Context When working on a new version of RHEL (with Ruby 3.0), the requirement is to have a better security (remove unsafe digests or limit the use for non-security purposes). This would be achieved with using OpenSSL 3.0 as well, wh...pvalena (Pavel Valena)
I have a new student learning Ruby, and there are apparent inconsistencies in Ruby documentation. The problem appears to be in the order of parameters / variables `self` and `other_string`. <=> https://docs.ruby-lang.org/en/3.0.0/St...pvalena (Pavel Valena)
It is marked as unsafe by our static analysis. Can it be removed now? It was deprecated in: https://bugs.ruby-lang.org/projects/ruby-master/repository/trunk/revisions/60266 https://bugs.ruby-lang.org/issues/13097pvalena (Pavel Valena)
The `gem build` command requires gem files located in the directory where .gemspec file is. Introduced with Merge RubyGems 3.0.0.beta1[1], specifically ` Dir.chdir(File.dirname(gemspec)) do`. On Fedora[2], this results in pa...pvalena (Pavel Valena)