Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 15 submissions in the queue.
posted by CoolHand on Wednesday April 15 2015, @04:52AM   Printer-friendly
from the it's-the-end-of-the-web-as-we-know-it-and-i-feel-fine dept.

Phoronix reports the Mozilla Security Engineering team is planning to make their browser useless for browsing much of the World Wide Web, by deprecating insecure HTTP.

Richard Barnes of Mozilla writes:

In order to encourage web developers to move from HTTP to HTTPS, I would like to propose establishing a deprecation plan for HTTP without security. Broadly speaking, this plan would entail limiting new features to secure contexts, followed by gradually removing legacy features from insecure contexts. Having an overall program for HTTP deprecation makes a clear statement to the web community that the time for plaintext is over -- it tells the world that the new web uses HTTPS, so if you want to use new things, you need to provide security.

See also this document outlining the initial plans.

 
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: 2) by captain normal on Wednesday April 15 2015, @05:40AM

    by captain normal (2205) on Wednesday April 15 2015, @05:40AM (#170777)

    Guess that means you can't see soylentnews.org on FF.

    --
    When life isn't going right, go left.
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 0) by Anonymous Coward on Wednesday April 15 2015, @05:45AM

    by Anonymous Coward on Wednesday April 15 2015, @05:45AM (#170781)

    It's fine and dandy. [soylentnews.org] You must be thinking of the other place.

  • (Score: 5, Informative) by frojack on Wednesday April 15 2015, @05:47AM

    by frojack (1554) on Wednesday April 15 2015, @05:47AM (#170782) Journal

    https works for soylentnews.org.

    I use it that way all the time. Not for any good reason.

    --
    No, you are mistaken. I've always had this sig.
    • (Score: 5, Insightful) by c0lo on Wednesday April 15 2015, @06:37AM

      by c0lo (156) Subscriber Badge on Wednesday April 15 2015, @06:37AM (#170803) Journal

      Not for any good reason.

      How about for the reason of increasing the "encrypted noise" traffic, to make the detection of "encrypted, thus possible tasty, transmission" a bit harder for the snoops.

      Be it only for increasing the pressure on various censoring firewalls of various countries in this world (pressure to move the majority of Web sites to "encrypted by default"). We'll take care of SSL's and CA's shortcomings a bit later, but let's start this journey, shall we?

      --
      https://www.youtube.com/watch?v=aoFiw2jMy-0 https://soylentnews.org/~MichaelDavidCrawford
    • (Score: 2) by captain normal on Wednesday April 15 2015, @03:50PM

      by captain normal (2205) on Wednesday April 15 2015, @03:50PM (#171023)

      I stand corrected. When I saw this yesterday I entered https://soylentnews.org [soylentnews.org] in the address bar and got a site not found return. This morning when I read your reply, I tried again and it loaded. I do remember a few months ago there was some discussion about SN using a secure connection.
      Likewise, I can't think of any good reason. SN doesn't host email nor do direct financial transactions.

      --
      When life isn't going right, go left.
    • (Score: 0) by Anonymous Coward on Wednesday April 15 2015, @10:09PM

      by Anonymous Coward on Wednesday April 15 2015, @10:09PM (#171205)

      Of course there's a good reason. SoylentNews and any other site that has logins would be irresponsible to not support HTTPS in order to mitigate the Firesheep [wikipedia.org] attack which sniffs login cookies from public wifi.

      That said, I'd argue any site should be using HTTPS to prevent activate attacks that inject malicious code or ads.