Skip to content
  1. Feb 14, 2014
  2. Feb 10, 2014
  3. Feb 09, 2014
  4. Feb 07, 2014
    • Andreas Fuchs's avatar
      Install libyaml 0.1.5 for 2.x rubies also · 45067e75
      Andreas Fuchs authored
      This should plug the vulnerability to CVE-2013-6393 (and fix #504)
      that can still occur in certain systems: If the ruby build process
      couldn't find a libyaml that worked, it would build its own vendored
      libyaml, which was 0.1.4 (and is vulnerable).
      
      Instead, specify that the build always should install the latest
      libyaml & build against that.
      45067e75
  5. Feb 04, 2014
  6. Feb 03, 2014
  7. Jan 29, 2014
  8. Jan 23, 2014
  9. Jan 22, 2014
  10. Jan 17, 2014
  11. Jan 09, 2014
  12. Jan 07, 2014
  13. Jan 06, 2014
  14. Jan 05, 2014
Loading