Skip to content
Snippets Groups Projects

updating rails to 3.2.10 in response to CVE-2012-5664

Merged updating rails to 3.2.10 in response to CVE-2012-5664
github/fork/dvanduzer/4-0-stable into 4-0-stable
Merged gitlab-qa-bot requested to merge github/fork/dvanduzer/4-0-stable into 4-0-stable

Created by: dvanduzer

See also: https://github.com/gitlabhq/gitlabhq/issues/2464 http://www.securityfocus.com/bid/57084

Additional notes!

  • The Vagrant VM rvm's the latest Ruby instead of recommended (and working) ruby-1.9.3-p327

  • DB setup/teardown isn't automatic. i.e. this is required:

    $ bundle exec rake gitlab:app:setup RAILS_ENV=test

Anyway, this commit doesn't change anything beyond upgrading rails. All tests currently passing.

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • gitlab-qa-bot
    gitlab-qa-bot @gitlab-qa-bot ·
    Author Owner

    Created by: mathgl67

    I try the the patch and have seen no problem at the moment. Thanks dvanduzer !

    By Administrator on 2013-01-06T10:52:56 (imported from GitLab project)

    By Administrator on 2013-01-06T10:52:56 (imported from GitLab)

Please register or sign in to reply