Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Tuesday May 08 2018, @11:56PM   Printer-friendly
from the ain't-no-control dept.

Submitted via IRC for SoyCow3941

We think of our job as controlling the user's experience. But the reality is, we control far less than we imagine.

Last week, two events reminded us, yet again, of how right Douglas Crockford was when he declared the web "the most hostile software engineering environment imaginable." Both were serious enough to take down an entire site—actually hundreds of entire sites, as it turned out. And both were avoidable.

[...] The first of these incidents involved the launch of Chrome 66. With that release, Google implemented a security patch with serious implications for folks who weren't paying attention. You might recall that quite a few questionable SSL certificates issued by Symantec Corporation's PKI began to surface early last year. Apparently, Symantec had subcontracted the creation of certificates without providing a whole lot of oversight. Long story short, the Chrome team decided the best course of action with respect to these potentially bogus (and security-threatening) SSL certificates was to set an "end of life" for accepting them as secure. They set Chrome 66 as the cutoff.

So, when Chrome 66 rolled out (an automatic, transparent update for pretty much everyone), suddenly any site running HTTPS on one of these certificates would no longer be considered secure. That's a major problem if the certificate in question is for our primary domain, but it's also a problem it's for a CDN we're using. You see, my server may be running on a valid SSL certificate, but if I have my assets—images, CSS, JavaScript—hosted on a CDN that is not secure, browsers will block those resources. It's like CSS Naked Day all over again.

To be completely honest, I wasn't really paying attention to this until Michael Spellacy looped me in on Twitter. Two hundred of his employer's sites were instantly reduced to plain old semantic HTML. No CSS. No images. No JavaScript.

The second incident was actually quite similar in that it also involved SSL, and specifically the expiration of an SSL certificate being used by jQuery's CDN. If a site relied on that CDN to serve an HTTPS-hosted version of jQuery, their users wouldn't have received it. And if that site was dependent on jQuery to be usable ... well, ouch!

It can be easy to shrug off news like this. Surely we'd make smarter implementation decisions if we were in charge. We'd certainly have included a local copy of jQuery like the good Boilerplate tells us to. The thing is, even with that extra bit of protection in place, we're falling for one of the most attractive fallacies when it comes to building for the web: that we have control.

Source: http://alistapart.com/article/the-illusion-of-control-in-web-design


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 3, Touché) by Anonymous Coward on Wednesday May 09 2018, @12:10AM (6 children)

    by Anonymous Coward on Wednesday May 09 2018, @12:10AM (#677260)

    And the moral of this story is: control your own assets (and destiny). If you are responsible for websites that use SSLs, or rely on CDNs that use SSLs, then you should make sure the partners you rely on are using valid SSLs. If you can't be sure about the reliability of your partners then protect yourself by controlling what you can control.

    When the Symantec debacle came to light we made sure all of our partners were not using Symantec certs. We contacted the two that were and made sure that they got new SSLs, and not just because of Google announcing that it would stop accepting those certificates at a future date. If the Symantec certificates were untrustworthy then they shouldn't be used whether or not Google, Mozilla, Apple, Microsoft, etc would stop accepting them.

    This isn't rocket science. When you are responsible for mission critical portions of your business (or your employer's business) you either pay attention or you pay the price.

    Starting Score:    0  points
    Moderation   +3  
       Insightful=1, Touché=2, Total=3
    Extra 'Touché' Modifier   0  

    Total Score:   3  
  • (Score: 5, Insightful) by The Mighty Buzzard on Wednesday May 09 2018, @12:13AM (3 children)

    That kind of anti-cloud heresy is no way to get yourself employed by a major tech company. It is, however, a good way to get yourself employed by a smaller, non-tech shop that will appreciate the hell out of you, pay you pretty well, and not work your entire ass off.

    --
    My rights don't end where your fear begins.
    • (Score: 0) by Anonymous Coward on Wednesday May 09 2018, @01:34AM

      by Anonymous Coward on Wednesday May 09 2018, @01:34AM (#677284)

      While we may not agree on a whole hell of a lot it is nice to see some techies who don't like JS for everything and relying on other people's services.

    • (Score: 0) by Anonymous Coward on Wednesday May 09 2018, @02:30AM (1 child)

      by Anonymous Coward on Wednesday May 09 2018, @02:30AM (#677307)

      It is, however, a good way to get yourself employed by a smaller, non-tech shop that will appreciate the hell out of you, pay you pretty well, and not work your entire ass off.

      It's like you know me.

      • (Score: 3, Interesting) by The Mighty Buzzard on Wednesday May 09 2018, @03:29AM

        To take it to the next step you find yourself enough even smaller shops that have no need of a full time admin but do need someone, then sell them N hours per month of presence (may as well do general upkeep and look into a few complaints while you're there, maybe bring donuts) and a moderate extra fee if you have to work over those number of hours. Repeat until you find a happy balance between money and time for doing whatever the hell you feel like. Or repeat until you've had to take on dozens of helpers in many locations then sell the company for a fat wad of cash and retire.

        --
        My rights don't end where your fear begins.
  • (Score: 1, Interesting) by Anonymous Coward on Wednesday May 09 2018, @12:23AM

    by Anonymous Coward on Wednesday May 09 2018, @12:23AM (#677266)

    No, the moral of the story is that HTTPS is bullshit. But it does serve very well for tracking purposes. The web should be pure HTML and nothing more.

  • (Score: 4, Interesting) by c0lo on Wednesday May 09 2018, @12:41AM

    by c0lo (156) on Wednesday May 09 2018, @12:41AM (#677272) Journal

    And the moral of this story is: control your own assets (and destiny)

    Huh! If that would be that simple.
    You reckon the control over assets is enough? To paraphrase:

    Tell me, Mr. Anderson, what good is the control over your mouth when you don't have a proper phone connection?

    Yes, I know you never said that, but the context is 'illusion of control' - your answer suggest a better way to deal with, but if one imagins that's foolproof, the illusion of control will still persists.

    And I tell you a more reliable way to make sure the access to your assets doesn't depend as much on others. It involves relinquishing most of the control on your assets - replicate them in a P2P network and let many independent third parties certify their authenticity (use of a DHT).
    Of course this is barely possible in the today's mainstream internet, having control' drives profits and power for those able to exercise it.

    --
    https://www.youtube.com/watch?v=aoFiw2jMy-0