On Tuesday, 2 September 2014 22:58:58 UTC-4, M,Gopi M.gopinath wrote:
>
> Hi Jason,
>
> Thanks for your reply, here is link which says run time dependencies 
> google-tag-manager needs rails >=3.0.0.
>
>
> https://github.com/rcs/google-tag-manager-rails/blob/master/google-tag-manager-rails.gemspec
>
> https://rubygems.org/gems/google-tag-manager-rails
>
> website have been build 8 yrs back, Now I am maintaining this, they did't 
> upgrade this current version or atleast rails 3.0.0.
>
> One more question, 
>
> Whether is there any possibilities to implement google-tag-manager without 
> gem. in ruby 1.8.6 and rails 2.3.5
>
>
There's not much code in that gem; looks like the reason it requires 
>=3.0.0 is that it needs to register a helper, which changed radically 
between 2.3.x and 3.0. It may be easier to just copy the relevant bits 
directly into the application.

Regarding the upgrade, you should at the very least either get onto 2.3.16 
or manually apply the fixes for CVE-2013-0156 and CVE-2013-0333:

https://groups.google.com/forum/#!topic/rubyonrails-security/61bkgvnSGTQ
https://groups.google.com/forum/#!topic/rubyonrails-security/1h2DR63ViGo

Failing to do so leaves your server vulnerable to a remote-code-execution 
attack that can be triggered with a single request.

Here's a guide to upgrading step-by-step through the 2.3.x series. Haven't 
tried it, but the steps seem reasonable.

http://makandracards.com/makandra/16951-upgrading-rails-2-from-2-3-8-through-2-3-18-to-rails-lts

--Matt Jones

-- 
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 rubyonrails-talk+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-talk/11967267-05d7-44e4-8cb6-2a6e8f71ea44%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to