News for hackers. Stuff that matters.
Re:Use LetsEncrypt and CloudFlare to secure any Heroku app f... by samwillis on Thursday July 21, 2016 @11:31AM (#12137501)
Do also keep in mind that ssl on Heroku is terminated at their routing layer before your Dynos. Therefore it is as easy for Heroku (Salesforce) to man-in-the-middle your application as it is for CloudFlare, whether that be on instruction for the authorities or due to a bad actor on the staff.

Both of them you have to trust to do the right thing and that is an exercise left to the individual thinking of using either service. So lets not pretend that CloudFlare is a special case.

If you need to trust the none of your service providers can MITM your site then you can't use any PaaS or CDN, you need to terminate the SSL yourself, that includes for all static assets you use. No more jQuery from Google CDN, no more analytics/exception tracking/fonts from your favoured provider and no more advertising conversion tracking.

But then do also remember that it's possible for any web host to take over their customers site as long as they own the IP address. They just point the IP to another server, configure it to respond to the hostname and they can then even use any SSL certificate provider who validates the domain name with a file at a specific URL to grab a certificate.

Everyone has to make their own judgment on who they can trust. CloudFlare is no different.

Re:Use LetsEncrypt and CloudFlare to secure any Heroku app f... by dublinben on Thursday July 21, 2016 @12:40PM (#12138048)
>No more jQuery from Google CDN, no more analytics/exception tracking/fonts from your favoured provider and no more advertising conversion tracking

Those all sound like reasonable best practices for building a website.

Re:Use LetsEncrypt and CloudFlare to secure any Heroku app f... by JohnTHaller on Thursday July 21, 2016 @12:50PM (#12138145)
Except for the part where anyone you'd like to partner with isn't going to trust your internal analytics to gauge your popularity. One of the points of third party analytics is that you have a disinterested third party who can provide the data to someone else.
Re:Use LetsEncrypt and CloudFlare to secure any Heroku app f... by samwillis on Thursday July 21, 2016 @01:48PM (#12138627)
If I use self hosted analytics and exception tracking I have to ensure its up-to-date with security patches. The pros will do a better job at this than anyone will self hosting. Concentrate on your core business, knowing when to outsource is important.

As someone running an ecommerce website without using advertising conversion tracking from to our various advertising networks it would simply not be measurable or cost effective. It is an essential part of how the systems works.

Re:Use LetsEncrypt and CloudFlare to secure any Heroku app f... by superuser2 on Thursday July 21, 2016 @03:34PM (#12139412)
>Therefore it is as easy for Heroku (Salesforce) to man-in-the-middle your application as it is for CloudFlare

Heroku owns your server and can just as easily read your database off disk and/or your webserver process's memory. If you don't want to trust an infrastructure provider, you need to have physical control of your server. Such quibbles about architecture are deck chairs on the Titanic.

Re:Use LetsEncrypt and CloudFlare to secure any Heroku app f... by Perceptes on Thursday July 21, 2016 @04:09PM (#12139660)
In one sense that's true, but as they say in the security field, the fact that someone could break down your home's front door with an axe doesn't keep us from locking our doors. Even if you generally trust your infrastructure provider, there's still no harm in considering the different layers at which you are and are not protected from certain attacks. For example, a single rogue employee might be able to do some harm in one area, but not another.
Re:Use LetsEncrypt and CloudFlare to secure any Heroku app f... by petrosagg on Thursday July 21, 2016 @10:26PM (#12141354)
>No more jQuery from Google CDN, no more analytics/exception tracking/fonts from your favoured provider and no more advertising conversion tracking

You don't have to trust the CDN for any static resource you load as long as you use the subresource integrity feature of modern browsers[1]. You basically include the hash of the content on your main domain and the browser will validate it when it loads it from CDN. So you only need to trust your main site.

[1] https://developer.mozilla.org/en-US/docs/Web/Security/Subres...

Edit: It was already mentioned by michaelmior https://news.ycombinator.com/item?id=12138277

Re:Use LetsEncrypt and CloudFlare to secure any Heroku app f... by michaelmior on Thursday July 21, 2016 @01:04PM (#12138277)
In terms of using resources from a CDN, you can (sort of) make use of subresource integrity [0]. Browser support isn't great yet though I believe.

[0] https://developer.mozilla.org/en-US/docs/Web/Security/Subres...

Re:Use LetsEncrypt and CloudFlare to secure any Heroku app f... by king_phil on Thursday July 21, 2016 @05:07PM (#12140084)
With the exception that MITM between cloudflare and the origin has been seen in the wild and documented and MITM on/in the heroku network has not.
Re:Use LetsEncrypt and CloudFlare to secure any Heroku app f... by dwaltrip on Friday July 22, 2016 @01:21PM (#12145017)
I'm guessing this is not a worry for a digital ocean droplet. Do you know if that is the case?