3 ms·
> AES-NI doesn't work on ARM, which is what we have. I'm afraid this falls into scope of the low-priority issue 4299 then: https://code.google.com/p/go/issues/
by tagrun 12y ago
> AES-NI doesn't work on ARM, which is what we have.
I'm afraid this falls into scope of the low-priority issue 4299 then: https://code.google.com/p/go/issues/detail?id=4299 https://code.google.com/p/go/issues/detail?id=4299
> OpenSSL allows you to specify your own validation callback, to add additional checks to the certificate validation step. The only certificate validation option Go's TLS gives you is either InsecureSkipVerify or not.
I'm not sure about the necessity or the details of the particular use case, but if it is general enough, you can file an issue.
- jtolds 12y agoThanks for the pointer to #4299. Unfortunately, custom asm isn't going to be nearly as fast as what we're doing, but I left a comment to that affect. As for adding options to Go TLS, it is worth filing an issue for sure. Go 1 compatibility guarantee (and resulting standard library interface freeze) definitely restricts options here, but yeah I'll look into it.