-
Notifications
You must be signed in to change notification settings - Fork 233
[DOC] Add security documentation #3928
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
|
||
| - Execute any code in your Gemfile (Gemfiles are Ruby code) | ||
| - Install gems specified in the Gemfile, which may include native extensions that execute during installation | ||
| - Run any post-install hooks defined by gems |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does RubyGems allow for post-install hooks? I thought you could only show messages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not a direct post-install hook. But you can use spec.rdoc_options to specify what RDoc should run to generate your gem's documentation for ri (which will be invoked by rubygems), including running your rdoc options etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really? I had no idea.
0c4d52d to
c310ff3
Compare
c310ff3 to
1603db0
Compare
|
|
||
| - Execute any code in your Gemfile (Gemfiles are Ruby code) | ||
| - Install gems specified in the Gemfile, which may include native extensions that execute during installation | ||
| - Run any post-install hooks defined by gems |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really? I had no idea.
Co-authored-by: Vinicius Stock <vinistock@users.noreply.github.com>
Motivation
Ruby LSP, by design, can execute code (e.g. run
bundle install) when the user simply opening the project in VS Code under trusted mode. This is necessary for usability and it's a common practice among language servers and their extensions. But the risk should be clearly communicated with users.Implementation
Add a page to document known (but not exhaustive) code executions that could be performed by Ruby LSP so users can be aware of the potential risks.
Automated Tests
Manual Tests