-
Notifications
You must be signed in to change notification settings - Fork 66
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
Permissions incorrect in safe_yaml-0.9.2.gem #40
Comments
What?! Ugh, how did I let that happen? Embarrassing. I will fix this later today. Unfortunately I'm on vacation in Croatia without consistent internet access at the moment. In the meantime I guess the only option for users installing SafeYAML as a system gem is to manually repair the permissions :( |
It happens! Oddly enough, the modified date of the file is 1969-01-01 also. Something funky happened. On Jun 4, 2013, at 22:34, Dan Tao [email protected] wrote:
|
Also found this issue when using on default mac ruby 1.8.7. |
To make ticket this more googlable, here's an error message from this issue:
found at test-kitchen/test-kitchen#137 |
OK, this should be fixed in version 0.9.3 (kinda weird to create a new version just for file permissions, but that seemed the most expedient solution to me). |
Can you also yank 0.9.2? If there are no other changes in 0.9.3 than permissions, there should be no reason to continue having folks use it. |
@josephholsten Agreed—done. |
Adjust octokit v2 interface
In the last release of the gem, the
lib/safe_yaml.rb
file has mode 640. This makes it unreadable (thus unusable) by normal users when installed by root as a system gem.The text was updated successfully, but these errors were encountered: