4 ms·
The DAY I manage to convince the big wigs where I work that we should switch from a typical shared environment to Heroku, this happens. Talk about luck. :( Ho
by sergiotapia 14y ago
The DAY I manage to convince the big wigs where I work that we should switch from a typical shared environment to Heroku, this happens.
Talk about luck. :(
Hopefully I can spin this and not leave a bad taste in their mouths. We (engineers) understand what's happening, management doesn't and they don't give a shit.
- tomjen3 14y agoWhat is the alternative? You stay on the shared hosting and then what, you get hacked because you didn't verify a gem? Are the bigwigs going to authorize you time to look through all gems for potential backdoors or are they going to get i for free with their Heroku hosting?
- AlexMuir 14y agoSafe by default. That's your angle. It's additional effort to deploy dangerous code.
- sumone4life 14y agothey give you a straight forward workaround to still deploy. They just make you set a value explicitly so they know you are aware of the risk. Good to know someone is watching your back :)
- agotterer 14y agoThe exploit still exists whether you are on Heroku, shared or bare metal hosting environment. It's not an issue specific to Heroku, it's an issue that affects ruby gems. Your situation would be worse if you convinced the big wigs to switch to Ruby today.
- rrikhy 14y agoFeel free to reach out to me if you'd like to have a conversation about how to support your case on Heroku or if you have any questions/concerns; raj@heroku.com
- pardner 14y agoFrom a manager perspective, this sort of alert (as well as recent Heroku emails telling you specifically which app(s) needed patching for the recent Rails CVE issues) is a great example of one of the extra benefits of Heroku. A team of engineers 'watching your back' at no extra charge is a good thing.
- cobrabyte 14y agoAgreed. I was surprised when I received an email from Heroku letting me know that a few of my apps needed to be updated after the Rails vulnerabilities were uncovered. They also named the apps that needed to be updated, which makes my job that much simpler.
- kawsper 14y agoIt was a nice service with the mail. But it was sent one day after the exploit was out in the open, which is too late, but better than nothing.
- jordanthoms 14y agoI guess they had to build the feature. With the follow-on exploit for rails <3.1, the notification email went out very quickly and probably they will have quick notifications going forward.
- btown 14y ago"Thank goodness we switched to Heroku. Had we stayed on our previous environment, we would have been opened up to a security exploit without even knowing it."
- railsblob 14y agoBe c0ol. iT takse gut to take on the javacs in theys enterprizes. Yuo has tanken th furst step in Rubby enligtenmont in youse employmenter. So, whos is a few bugs? I has bet that DDT has crasehd his supr cool turboo charegd racecar and drived agin to proof his not afrid of anytang (DDT iz d a bomb). Yuse has a hng in ther an tell evbody how greta Rubby is. Peepl will see, they is not stpid. Javacs is cowering in fear. Even Rubby bugs ar more scarier than ayn Javacs bugs! (I membre frtsi time I saw a Rubby bug in my cdoe. IUt was a code smell bu t I kilt it wthi a desgn patren)