Sergey Frolov

This is a terrific solution. I'd like to get a wrapper like this into uTLS.

[Comments above](https://github.com/refraction-networking/utls/issues/16#issuecomment-455982018) describe a proper solution. This wrapper had not been implemented in uTLS yet. 

There are no such plans, but I am happy to accept a PR, that allows users to specify a padding scheme. I am open to suggestions on API, but a...

Looks like we'll need to copy a config file for this architecture from standard's go lib to `cpu` folder of this repo

Could be a server issue. Did you take a look at which `unexpected message` is it in wireshark?

When I visit https://104.27.159.141 in Chrome 83 I get this: ``` This site can’t provide a secure connection 104.27.159.141 uses an unsupported protocol. ERR_SSL_VERSION_OR_CIPHER_MISMATCH Unsupported protocol The client and server...

Perhaps we can. Or perhaps @Yawning can agree to dual license his uTLS changes so we can pull them here. I am pretty busy right now, since I have a...

Looks like we'll need to copy a config file for this architecture from standard's go lib to `cpu` folder of this repo

BoringSSL test runner does seem like a useful addition to uTLS.

What's wrong with calling Handshake? This is an unusual use-case with client connecting, and waiting for server to send data. On Thu, Apr 1, 2021, 01:56 Hirbod Behnam ***@***.***> wrote:...