# Google is experimenting with post-quantum crypto for TLS

**URL:** <https://community.letsencrypt.org/t/google-is-experimenting-with-post-quantum-crypto-for-tls/17720>\
**Category:** Server\
**Created:** [July 8, 2016, 9:23am UTC](https://community.letsencrypt.org/t/google-is-experimenting-with-post-quantum-crypto-for-tls/17720 "2016-07-08T09:23:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rugk](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rugk/32/19612_2.png) [@rugk](https://community.letsencrypt.org/u/rugk)\
**Post date:** [July 8, 2016, 9:23am UTC](https://community.letsencrypt.org/t/google-is-experimenting-with-post-quantum-crypto-for-tls/17720/1 "2016-07-08T09:23:33Z")

</div>

When powerful quantum-computers will be possible in the future they will also able to break RSA, Diffie-Hellman and elliptical curves and can even decrypt traffic recorded right in the past (i.e. now e.g.). Therefore there is a need for [post-quantum cryptography](https://en.wikipedia.org/wiki/Post-quantum_cryptography).

There is still much need for scientific research in this topic, but Google has already began implementing a key exchange, which may be secure against quantum attacks. It’s name is “New Hope”.  
As the key exchange may be weaker than though and may turn out to be breakable by current computers Google combines it with a [X25519](https://en.wikipedia.org/wiki/Curve25519) key exchange, to protect users. They call this hybrid mode _CECPQ1_ and it is currently implemented [BoringSSL](https://boringssl.googlesource.com/boringssl/+/e25775bcacb120f7f501a61d78a622ba429ba5d9) and used in Chrome Canary.

BTW also Tor [is discussing the use of CECPQ1](https://gitweb.torproject.org/user/isis/torspec.git/tree/proposals/XXX-newhope-hybrid-handshake.txt?h=draft/newhope).

More information:

> **[Google Tests New Crypto in Chrome to Fend Off Quantum Attacks](https://www.wired.com/2016/07/google-tests-new-crypto-chrome-fend-off-quantum-attacks/)**
>
> The web giant is rolling out the biggest-ever test of encryption designed to be resistant to a sci-fi future threat: a codebreaking quantum computer.

  

> **[Experimenting with Post-Quantum Cryptography](https://security.googleblog.com/2016/07/experimenting-with-post-quantum.html)**
>
> Posted by Matt Braithwaite, Software Engineer Quantum computers are a fundamentally different sort of computer that take advantage of aspec...

There is also German article: [http://www.golem.de/news/new-hope-google-testet-post-quanten-algorithmus-1607-121989.html](http://www.golem.de/news/new-hope-google-testet-post-quanten-algorithmus-1607-121989.html)

---

<div class="post-metadata">

**Author:** ![ecdsa-chacha20](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/ecdsa-chacha20/32/955_2.png) [@ecdsa-chacha20](https://community.letsencrypt.org/u/ecdsa-chacha20)\
**Post date:** [July 8, 2016, 10:57am UTC](https://community.letsencrypt.org/t/google-is-experimenting-with-post-quantum-crypto-for-tls/17720/2 "2016-07-08T10:57:26Z")

</div>

Sounds like an interesting idea, especially the implementation of and fallback to X25519. Are there known patches for CECPQ1 for OpenSSL?

BTW, your link to the [googleblog.com](http://googleblog.com) article contains an unsecure image, hence this page gets a security warning.

---

<div class="post-metadata">

**Author:** ![pfg](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/pfg/32/1924_2.png) [@pfg](https://community.letsencrypt.org/u/pfg)\
**Post date:** [July 8, 2016, 11:02am UTC](https://community.letsencrypt.org/t/google-is-experimenting-with-post-quantum-crypto-for-tls/17720/3 "2016-07-08T11:02:58Z")

</div>

> [@ecdsa-chacha20](#):
>
> Are there known patches for CECPQ1 for OpenSSL?

Google implemented it in BoringSSL [here](https://github.com/google/boringssl/commit/e25775bcacb120f7f501a61d78a622ba429ba5d9). Not sure if that patch can easily be merged in OpenSSL or whether BoringSSL diverged too much for that to work without a lot of extra work.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [August 7, 2016, 2:15pm UTC](https://community.letsencrypt.org/t/google-is-experimenting-with-post-quantum-crypto-for-tls/17720/5 "2016-08-07T14:15:09Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
