'gem build' should warn on restrictive permissions #191
Labels
Comments
ghost
assigned 
|
This should be an easy feature to add. Without a patch it will be closed though ☹ |
|
OK. That's fair. Here's a pull request. |
|
Closing this for now... if others desire executable checking they should reopen and add. |
|
This would help address a number of issues regarding gems and permissions. #191 rubygems/bundler#2136 |
|
The executable checking appears to be implemented by @0f2cacc2 (the tests for the feature, at least) |
nobu
pushed a commit
to nobu/rubygems
that referenced
this issue
Jan 12, 2014
Check $! after Dir.exists? returns false.
phw
added a commit
to phw/ruby-discid
that referenced
this issue
Aug 27, 2015
Obviously gem uses the permissions set locally and applies them to the packaged files. Obviously this is a gem issue, but gem developers are ignorant on this. See: rubygems/rubygems#272 rubygems/rubygems#707 rubygems/rubygems#191 and related issues.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Usually you'll always want to allow access to anyone in your group or even everyone on the system access to your gem. it would be a nice feature if 'gem build' warned when you built a gem with restrictive permissions. We've had a few instances where this wasn't caught and it causes issues when people try to start script/console and similar things.
The text was updated successfully, but these errors were encountered: