Stories
Slash Boxes
Comments

SoylentNews is people

Transport Layer Security Version 1.3 Approved

posted by mrpg on Monday March 26 2018, @11:07AM   Printer-friendly
from the Certificate-verification-failed dept.

takyon writes:

The web will soon be a little safer with the approval of this new security standard

TLS 1.3 makes a few prominent changes that should keep you safe.

  • The "handshake" between client and server has been streamlined and encryption initiated earlier to minimize the amount of data transmitted in the clear.
  • "Forward secrecy," meaning hackers can't skim decryption keys from one exchange and use it to decrypt others later.
  • "Legacy" encryption algorithms have been removed as options, as these could occasionally be forced into use and their shortcomings leveraged to break the cipher on messages.
  • A new "0-RTT," or zero round-trip time, mode in which the server and client that have established some preliminaries before can get right to sending data without introducing themselves to each other again.

The whole standard is 155 pages long, and really only other engineers will want to dig in. But it's available here if you'd like to peruse it or go into detail on one of the new features.

Also at The Register.

Original Submission

 
This discussion has been archived. No new comments can be posted.
Transport Layer Security Version 1.3 Approved | Log In/Create an Account | Top | 29 comments | Search Discussion
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: 0) by Anonymous Coward on Monday March 26 2018, @02:36PM (1 child)

    by Anonymous Coward on Monday March 26 2018, @02:36PM (#658444)

    Client certificates are about authenticating the client to the server. They could, in priciple, replace password dialogs on websites. They don't replace CAs.

    Privacy concerns with client certificates together with very poor browser support limits adoption on web services.

  • (Score: 2) by isostatic on Monday March 26 2018, @08:01PM

    by isostatic (365) on Monday March 26 2018, @08:01PM (#658626) Journal

    We use client certs all the time, MDM deploys them to devices (phones, laptops etc) every couple of months. On the server side install an internal .deb and include a file in your apache/nginx config, works fine on firefox and chrome (linux and mac) and safari (mac and osx) and curl, powers the F5 vpn too.

    What's not to like?