Results 1 to 8 of 8

Thread: HTTP/2 finalised says IETF HTTP Working Group chair

  1. #1
    HEXUS.admin
    Join Date
    Apr 2005
    Posts
    27,269
    Thanks
    0
    Thanked
    1,680 times in 584 posts

    HTTP/2 finalised says IETF HTTP Working Group chair

    The new protocol promises faster, less bandwidth sapping web browsing.
    Read more.

  2. #2
    Banned
    Join Date
    Jun 2008
    Posts
    2,129
    Thanks
    13
    Thanked
    189 times in 160 posts

    Re: HTTP/2 finalised says IETF HTTP Working Group chair

    Easier to snoop on.... yay!

    NOT.

  3. #3
    Senior Member watercooled's Avatar
    Join Date
    Jan 2009
    Posts
    10,514
    Thanks
    1,476
    Thanked
    886 times in 768 posts

    Re: HTTP/2 finalised says IETF HTTP Working Group chair

    How do you work that one out? If anything, HTTP2 makes cryptography more accessible.
    Last edited by watercooled; 18-02-2015 at 05:40 PM.

  4. #4
    Banned
    Join Date
    Jun 2008
    Posts
    2,129
    Thanks
    13
    Thanked
    189 times in 160 posts

    Re: HTTP/2 finalised says IETF HTTP Working Group chair

    It uses 1 tcpip connection instead of multiples ones.

    Ie one less step in piecing it together.

  5. #5
    Senior Member watercooled's Avatar
    Join Date
    Jan 2009
    Posts
    10,514
    Thanks
    1,476
    Thanked
    886 times in 768 posts

    Re: HTTP/2 finalised says IETF HTTP Working Group chair

    Thus making the whole system far more efficient. However it's still muxed at a higher level, and the single TCP stream is just coincidental as far as privacy is concerned - that's what cryptography is for at the end of the day.

    If you're expecting parallel TCP connections to offer even a whiff of privacy you'll be sorely disappointed; reassembling streams is really quite trivial - it's what browsers and servers are doing all the time. Tools like Wireshark are quite good at it too. There's a chance some of the packets will find themselves on separate routes over longer connections but that's about it, and that still applies.

    It doesn't even make it to storm in a teacup TBH, it's a complete non-issue.

  6. #6
    IQ: 1.42
    Join Date
    May 2007
    Location
    old trafford
    Posts
    982
    Thanks
    115
    Thanked
    51 times in 49 posts
    • Tunnah's system
      • Motherboard:
      • Asus P8P67 PRO
      • CPU:
      • Core i7 2700K
      • Memory:
      • 12GB DDR3-1600
      • Storage:
      • Various SSDs, 90TB RAID6 HDDs
      • Graphics card(s):
      • 1080Ti
      • PSU:
      • Silverstone 650w
      • Case:
      • Lian-Li PC70B
      • Operating System:
      • Win10
      • Internet:
      • 40mbit Sky Fibre

    Re: HTTP/2 finalised says IETF HTTP Working Group chair

    Mate that is a massively uneducated statement and is nothing short of scare-mongering. HTTP/2 should be celebrated, please don't give people false ideas about security concerns you don't really know anything about

  7. #7
    Senior Member
    Join Date
    Jun 2004
    Location
    Kingdom of Fife (Scotland)
    Posts
    4,991
    Thanks
    393
    Thanked
    220 times in 190 posts
    • crossy's system
      • Motherboard:
      • ASUS Sabertooth X99
      • CPU:
      • Intel 5830k / Noctua NH-D15
      • Memory:
      • 32GB Crucial Ballistix DDR4
      • Storage:
      • 500GB Samsung 850Pro NVMe, 1TB Samsung 850EVO SSD, 1TB Seagate SSHD, 2TB WD Green, 8TB Seagate
      • Graphics card(s):
      • Asus Strix GTX970OC
      • PSU:
      • Corsair AX750 (modular)
      • Case:
      • Coolermaster HAF932 (with wheels)
      • Operating System:
      • Windows 10 Pro 64bit, Ubuntu 16.04LTS
      • Monitor(s):
      • LG Flattron W2361V
      • Internet:
      • VirginMedia 200Mb

    Re: HTTP/2 finalised says IETF HTTP Working Group chair

    Quote Originally Posted by abaxas View Post
    It uses 1 tcpip connection instead of multiples ones.
    Ie one less step in piecing it together.
    Yes, but on the flip side, they've moved to a binary format and added compression, which should mess up a casual sharking pretty well. Plus I've read elsewhere that the single TCP connection may make it easier to tunnel your session over a VPN, thereby adding encryption with less overhead and hassle.

    Career status: still enjoying my new career in DevOps, but it's keeping me busy...

  8. #8
    Member
    Join Date
    Mar 2014
    Posts
    113
    Thanks
    2
    Thanked
    7 times in 6 posts

    Re: HTTP/2 finalised says IETF HTTP Working Group chair

    Firefox and IE only support HTTP/2 over TLS, and Chrome's support for HTTP/2 is not enabled by default.

    Additionally hosting providers need to launch support for it at the server level. At the moment, neither Apache nor Nginx support HTTP/2.

    Fairly long way off?

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •