Re:Try to not play with these sliders
by sleepychu on Monday May 22, 2017 @04:31AM
(#14391923)
Had to enable 3 different external JS sources to get the page to work. I don't mind sites using CDNs but please try and reduce the surface for external threats!
[ Parent
| on HN ]
In case it's of any help to you, I use https://github.com/Synzvato/decentraleyes which had 2 of these 3 CDNs cached. And the 3rd (unpkg - an npmjs.com mirror) seemed not to be a hard requirement as far as I could tell.
Re:Try to not play with these sliders
by therealmarv on Monday May 22, 2017 @04:35AM
(#14391936)
are people doing this? What's the attack surface of a private hosted JS library vs. a well known TLS/SSL secured CDN for JS libraries? Threats are not restricted to CDNs.
Security theater, nerd-style.
Re:Try to not play with these sliders
by raverbashing on Monday May 22, 2017 @04:36AM
(#14391939)
CDNs are much more reliable than your avg. 'stuff.com' hosted js. It shouldn't be an issue
Re:Try to not play with these sliders
by SchizoDuckie on Monday May 22, 2017 @05:15AM
(#14392095)
This is a falsehood i've seen repeated over and over.
CDN's fail. You already have a connection to the 'stuff.com' self-hosted js. If your site is up but the cdn breaks you have another problem.
Also the perf win for using a shared cdn version of for instance jquery is totally overstated. See discussions here too: https://news.ycombinator.com/item?id=11549131
Re:Try to not play with these sliders
by raverbashing on Monday May 22, 2017 @07:37AM
(#14392676)
Thanks, I stand corrected
Re:Try to not play with these sliders
by martinknafve on Monday May 22, 2017 @04:41AM
(#14391965)
That would depend on what CDN you use and how it works. If the CDN is just a caching CDN in front of your own site then the CDN typically won't be any more secure than your own site.