1. Floren
    In April 2014, I had an interesting discussion with Google engineer Adam Langley about the ChaCha20 and Poly1305 implementation into current AXIVO OpenSSL packages. He recommended to proceed with caution. Basically, I would be on my own related to support because ChaCha cipher is likely to change during its IETF journal.

    He also mentioned there is a problem getting some Google TLS work out to the outside world and that he's working on what he hopes it can be a solution. The answer is BoringSSL (aspirational name), a fork marking a new direction for Google which has built over 70 patches for OpenSSL to use in their products, including Android and Chrome.

    Adam mentioned in his blog entry that Google are not aiming to replace OpenSSL as an open-source project. They will still be sending them bug fixes when they find them and they will be importing changes from upstream. Also, they will still be funding the Core Infrastructure Initiative and the OpenBSD Foundation.