Add encryption and signature verification algorithm ChaCha20-Poly1305. This algorithm is faster than AES128-CBC with software implementation without hardware acceleration. 
Google uses this algorithm everywhere, it means that there is a future behind this algorithm. Such a big company can not be wrong. Add ChaCha20-Poly1305 for SSH, SSTP, IPsesā¦
+1
Itās really odd this is not as requested feature. on the other hand, a lot of really requested features are overlooked as wellā¦
+1
chacha20-poly1305 is faster and safer than aes-cbc/aes-gcm.
One request per year, really necessaryā¦
We need to stop thinking about standardizing everything Google chooses.
-10000
This is funny. I suggest checking this page and seeing that often it is the exact opposite: https://killedbygoogle.com/
About ChaCha20-Poly1305 -MikroTik RouterOS uses it already in Wireguard. You can use that to have ChaCha.
Open standards adoption by big companies are not quite the same with discontinued services.
Why not? They can just as easily switch everything to something else, my comment is on this ābright futureā dream
Because open standards can be adopted by anyone, and even if Google decides to later stop using them and āchange everything to something elseā we can still use them. Discontinued proprietary services on the other handā¦ no. Hence, itās not quite the same.
All this noise about google is here because the original poster wrote this:
Whereas in fact it does not mean anything. So in this context āit is actually quite the sameā.
Thatās what I meant, yes
Any chance of supporting ChaCha20 in IPSEC or PPTP (even if itās Mikrotik specific and works only between two ROS devices)?
Wireguard overhead is just massive (60 bytes) compared to ESP and it have itās own quirksā¦