No problems, but I was investigating an issue about the etc
gem being activated too soon on Windows, and eventually run into some code in the operating_system.rb
file shipped by RubyInstaller2 that automatically creates an empty "system gemrc" file if it does not exist already:
I got curious about the potential security issue. Does it affect more platforms other than Windows? The way I see it, system configuration is precisely intended for sharing a configuration with all users, so it's intended that a user with permissions to write files in Gem::ConfigFile::SYSTEM_WIDE_CONFIG_FILE
can setup RubyGems configurations for all users. Also, it seems that the current implementation will still respect this global file if it's already there.
So I'm not fully clear about the security issue and I'm looking for a bit more insights.
Steps to reproduceCreate an empty Gemfile and observe that ruby -rbundler/setup -e 'puts Gem.loaded_specs["etc"]'
activates the etc
gem on Windows.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4