News for hackers. Stuff that matters.
Re:RubyGems.org gem replacement security vulnerability and ... by dcu on Wednesday April 06, 2016 @08:05PM (#11443462)
I just wrote a simple script to check the gems:

https://gist.github.com/dcu/3c06e4ab0e98158c5742c4fd2b31523d

Re:RubyGems.org gem replacement security vulnerability and ... by brightshiny on Friday April 08, 2016 @11:58PM (#11459832)
Thanks for this. I did some extra work on it (via someone else's fork) so it can run across multiple directories. I've too many projects lurking around to cd into all of them! I added some pretty colours too :)

https://gist.github.com/yb66/44b97baecbeec6900e039ffb9461d31...

Re:RubyGems.org gem replacement security vulnerability and ... by elcapitan on Thursday April 07, 2016 @04:03AM (#11445544)
Thanks!

Probably depending on version, it seems to be missing a

    require 'time'
    require 'json'
in my environment.
Re:RubyGems.org gem replacement security vulnerability and ... by revorad on Thursday April 07, 2016 @07:51AM (#11446487)
Thanks for this. So I ran this and found a bunch of unsafe gems. Do I report them to each gem author or to RubyGems security?
Re:RubyGems.org gem replacement security vulnerability and ... by dcu on Thursday April 07, 2016 @09:11AM (#11446926)
I think we should ask the gem owner to verify that everything is ok unless there's a new version. I updated the script to report if there is a new safe version available.
Re:RubyGems.org gem replacement security vulnerability and ... by davidradcliffe on Thursday April 07, 2016 @08:24AM (#11446653)
In this context "unsafe" only means not 100% verified.
Re:RubyGems.org gem replacement security vulnerability and ... by seanhandley on Thursday April 07, 2016 @03:38AM (#11445435)
This is really helpful - thanks!