<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: maxcaceres</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/maxcaceres.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2008-07-02T10:39:15+00:00</updated><author><name>Simon Willison</name></author><entry><title>Ruby's Vulnerability Handling Debacle</title><link href="https://simonwillison.net/2008/Jul/2/matasano/#atom-tag" rel="alternate"/><published>2008-07-02T10:39:15+00:00</published><updated>2008-07-02T10:39:15+00:00</updated><id>https://simonwillison.net/2008/Jul/2/matasano/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.matasano.com/log/1079/rubys-vulnerability-handling-debacle/"&gt;Ruby&amp;#x27;s Vulnerability Handling Debacle&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
The critical Ruby vulnerabilities are over a week old now but there’s still no good official patch (the security patches cause segfaults in Rails, leaving the community reliant on unofficial patches from third parties). Max Caceres has three takeaway lessons, the most important of which is to always keep a “last-known-good” branch to apply critical patches to.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/maxcaceres"&gt;maxcaceres&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/open-source"&gt;open-source&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/patches"&gt;patches&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/rails"&gt;rails&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ruby"&gt;ruby&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;&lt;/p&gt;



</summary><category term="maxcaceres"/><category term="open-source"/><category term="patches"/><category term="rails"/><category term="ruby"/><category term="security"/></entry></feed>