search

jnraine / munkiserver

Visit https://github.com/munkiserver/munkiserver for active development — this repository is no longer maintained
85 stars 27 forks source link

Update Gemfile to use Rails 3.2.11 #163

Closed Ginja closed 11 years ago

Ginja commented 11 years ago

Updated Gemfile to use Rails 3.2.11 as that is the recommended fix for the following vulnerability: https://groups.google.com/forum/#!topic/rubyonrails-security/61bkgvnSGTQ/discussion

jnraine commented 11 years ago

Did you get a chance to test this with the SFU munkiserver?

rickychilcott commented 11 years ago

I haven't tested this yet? But the Gemfile.lock should also be included in the commit. Right?

Sent from my iPhone

On Jan 9, 2013, at 7:33 PM, Jordan Raine notifications@github.com wrote:

Did you get a chance to test this with the SFU munkiserver?

— Reply to this email directly or view it on GitHub.

Ginja commented 11 years ago

I tested it. Everything looks good (uploading, downloading, destroying records, system reporting, etc...).

Opps, forgot that file. I also did a bundle update (for fun) afterwards and everything still looks OK. Shall I include that Gemfile.lock file or do you want me to submit the one from the server where I just did 'bundle update rails'.

jnraine commented 11 years ago

I think just the Gemfile.lock after a bundle install command

rickychilcott commented 11 years ago

Yeah. Lets not tempt fate :)

Ricky Chilcott

On Jan 9, 2013, at 8:30 PM, Jordan Raine notifications@github.com wrote:

I think just the Gemfile.lock after a bundle install command

— Reply to this email directly or view it on GitHub.