I read the release notes for the patch, and they specifically said that Rails 3.0 was not patched, and attached to that message were the patch files I was trying to use. One of the security alerts said that Rails 3 wasn't affected, but that was only one out of three. Yes, the errors I saw made it appear as though the patches had already been applied, at least in part.
Walter On Mar 19, 2013, at 9:59 AM, Frederick Cheung wrote: > > > On Monday, March 18, 2013 9:53:56 PM UTC, Walter Lee Davis wrote: > Anyone else having difficulty applying the latest security patches to Rails > 3.0.20? Both the css_sanitizer and the sanitize patch offered fail for me, on > a local, up-to-date clone of Rails. This could be my general newb-ness with > git am patching. Newb as in "never tried it before". > > What have you been doing? Is there a reason you don't want to use the > rails-3-0-stable branch which is up to date with all that ? > > Fred > > Thanks, > > Walter > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msg/rubyonrails-talk/-/zSs1lMexE3MJ. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
