• progress_activity cloud_sync

    Reconnection to the server…

    Movim cannot talk with the server, please try again later

  • back_to_tab fullscreen tile_small dialpad mic videocam switch_camera screen_share

    mic_none No sound detected from your microphone


    • Public subscriptions

    • chevron_right

      coopr8

    • chevron_right

      gabagoo

    • chevron_right

      kenu_demon

    • chevron_right

      coopr8

    • chevron_right

      gabagoo

    • chevron_right

      kenu_demon

    • chevron_right

      coopr8

    • chevron_right

      gabagoo

    • chevron_right

      kenu_demon

  • Register Login

    Movim

    movim.chatterboxtown.us


  • group_work rss_feed
    add Follow

    ArsTechnica

    • Ar chevron_right

      Google quantum-proofs HTTPS by squeezing 2.5kB of data into 64-byte space

      news.movim.eu / ArsTechnica • 28 February 2026 • 1 minute

    Google on Friday unveiled its plan for its Chrome browser to secure HTTPS certificates against quantum computer attacks without breaking the Internet.

    The objective is a tall order. The quantum-resistant cryptographic data needed to transparently publish TLS certificates is roughly 40 times bigger than the classical cryptographic material used today. Today’s X.509 certificates are about 64 bytes in size, and comprise six elliptic curve signatures and two EC public keys. This material can be cracked through the quantum-enabled Shor’s algorithm . Certificates containing the equivalent quantum-resistant cryptographic material are roughly 2.5 kilobytes. All this data must be transmitted when a browser connects to a site.

    The bigger they come, the slower they move

    “The bigger you make the certificate, the slower the handshake and the more people you leave behind,” said Bas Westerbaan, principal research engineer at Cloudflare, which is partnering with Google on the transition. “Our problem is we don’t want to leave people behind in this transition.” Speaking to Ars, he said that people will likely disable the new encryption if it slows their browsing. He added that the massive size increase can also degrade “middle boxes,” which sit between browsers and the final site.

    Read full article

    Comments

    • tagbiz & it tagbiz & it tagbiz & it taggoogle taggoogle taggoogle tagsecurity tagsecurity tagsecurity tagcertificate transparency tagcertificate transparency tagcertificate transparency taghttps taghttps taghttps tagmerkle trees tagmerkle trees tagmerkle trees tagshor's algorithm tagshor's algorithm tagshor's algorithm tagbiz & it tagbiz & it tagbiz & it taggoogle taggoogle taggoogle tagsecurity tagsecurity tagsecurity tagcertificate transparency tagcertificate transparency tagcertificate transparency taghttps taghttps taghttps tagmerkle trees tagmerkle trees tagmerkle trees tagshor's algorithm tagshor's algorithm tagshor's algorithm tagbiz & it tagbiz & it tagbiz & it taggoogle taggoogle taggoogle tagsecurity tagsecurity tagsecurity tagcertificate transparency tagcertificate transparency tagcertificate transparency taghttps taghttps taghttps tagmerkle trees tagmerkle trees tagmerkle trees tagshor's algorithm tagshor's algorithm tagshor's algorithm

    • Pictures 3 image

    • visibility
    • visibility
    • visibility
    • Ar chevron_right

      Google quantum-proofs HTTPS by squeezing 2.5kB of data into 64-byte space

      news.movim.eu / ArsTechnica • 28 February 2026 • 1 minute

    Google on Friday unveiled its plan for its Chrome browser to secure HTTPS certificates against quantum computer attacks without breaking the Internet.

    The objective is a tall order. The quantum-resistant cryptographic data needed to transparently publish TLS certificates is roughly 40 times bigger than the classical cryptographic material used today. Today’s X.509 certificates are about 64 bytes in size, and comprise six elliptic curve signatures and two EC public keys. This material can be cracked through the quantum-enabled Shor’s algorithm . Certificates containing the equivalent quantum-resistant cryptographic material are roughly 2.5 kilobytes. All this data must be transmitted when a browser connects to a site.

    The bigger they come, the slower they move

    “The bigger you make the certificate, the slower the handshake and the more people you leave behind,” said Bas Westerbaan, principal research engineer at Cloudflare, which is partnering with Google on the transition. “Our problem is we don’t want to leave people behind in this transition.” Speaking to Ars, he said that people will likely disable the new encryption if it slows their browsing. He added that the massive size increase can also degrade “middle boxes,” which sit between browsers and the final site.

    Read full article

    Comments

    • tagbiz & it tagbiz & it tagbiz & it taggoogle taggoogle taggoogle tagsecurity tagsecurity tagsecurity tagcertificate transparency tagcertificate transparency tagcertificate transparency taghttps taghttps taghttps tagmerkle trees tagmerkle trees tagmerkle trees tagshor's algorithm tagshor's algorithm tagshor's algorithm tagbiz & it tagbiz & it tagbiz & it taggoogle taggoogle taggoogle tagsecurity tagsecurity tagsecurity tagcertificate transparency tagcertificate transparency tagcertificate transparency taghttps taghttps taghttps tagmerkle trees tagmerkle trees tagmerkle trees tagshor's algorithm tagshor's algorithm tagshor's algorithm tagbiz & it tagbiz & it tagbiz & it taggoogle taggoogle taggoogle tagsecurity tagsecurity tagsecurity tagcertificate transparency tagcertificate transparency tagcertificate transparency taghttps taghttps taghttps tagmerkle trees tagmerkle trees tagmerkle trees tagshor's algorithm tagshor's algorithm tagshor's algorithm

    • Pictures 3 image

    • visibility
    • visibility
    • visibility
    • Ar chevron_right

      Google quantum-proofs HTTPS by squeezing 2.5kB of data into 64-byte space

      news.movim.eu / ArsTechnica • 28 February 2026 • 1 minute

    Google on Friday unveiled its plan for its Chrome browser to secure HTTPS certificates against quantum computer attacks without breaking the Internet.

    The objective is a tall order. The quantum-resistant cryptographic data needed to transparently publish TLS certificates is roughly 40 times bigger than the classical cryptographic material used today. Today’s X.509 certificates are about 64 bytes in size, and comprise six elliptic curve signatures and two EC public keys. This material can be cracked through the quantum-enabled Shor’s algorithm . Certificates containing the equivalent quantum-resistant cryptographic material are roughly 2.5 kilobytes. All this data must be transmitted when a browser connects to a site.

    The bigger they come, the slower they move

    “The bigger you make the certificate, the slower the handshake and the more people you leave behind,” said Bas Westerbaan, principal research engineer at Cloudflare, which is partnering with Google on the transition. “Our problem is we don’t want to leave people behind in this transition.” Speaking to Ars, he said that people will likely disable the new encryption if it slows their browsing. He added that the massive size increase can also degrade “middle boxes,” which sit between browsers and the final site.

    Read full article

    Comments

    • tagbiz & it tagbiz & it tagbiz & it taggoogle taggoogle taggoogle tagsecurity tagsecurity tagsecurity tagcertificate transparency tagcertificate transparency tagcertificate transparency taghttps taghttps taghttps tagmerkle trees tagmerkle trees tagmerkle trees tagshor's algorithm tagshor's algorithm tagshor's algorithm tagbiz & it tagbiz & it tagbiz & it taggoogle taggoogle taggoogle tagsecurity tagsecurity tagsecurity tagcertificate transparency tagcertificate transparency tagcertificate transparency taghttps taghttps taghttps tagmerkle trees tagmerkle trees tagmerkle trees tagshor's algorithm tagshor's algorithm tagshor's algorithm tagbiz & it tagbiz & it tagbiz & it taggoogle taggoogle taggoogle tagsecurity tagsecurity tagsecurity tagcertificate transparency tagcertificate transparency tagcertificate transparency taghttps taghttps taghttps tagmerkle trees tagmerkle trees tagmerkle trees tagshor's algorithm tagshor's algorithm tagshor's algorithm

    • Pictures 3 image

    • visibility
    • visibility
    • visibility
  • cloud_queue

    Powered by Movim