Whoops, yes, there is a feature flag there I missed "supportsAES" etc. It appears to be gated on that instruction being present, at which time the operation becomes roughly constant time.
M On Fri, 3 Dec 2021, 08:53 Matthew Walster, <matt...@walster.org> wrote: > Sure, it's enabled in a build constraint: > > > https://cs.opensource.google/go/go/+/refs/tags/go1.17.3:src/crypto/aes/cipher_asm.go > > It's not an exact science, there's no testing for the instruction afaict, > it's just that anything running the amd64 architecture has the aesni > instructions. I assume likewise for arm64. > > M > > On Fri, 3 Dec 2021, 05:51 Sean, <s.tolstoyev...@gmail.com> wrote: > >> Hello, >> >> Will **crypto/aes**, **cipher/GCM** work on hardware without embedded aes >> support? >> >> What I want to know is how these packages respond in cases where there is >> no embedded AES support (fast is not important). >> >> -- >> You received this message because you are subscribed to the Google Groups >> "golang-nuts" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to golang-nuts+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/golang-nuts/e55ee408-fdf3-4472-9e87-84647197ed73n%40googlegroups.com >> <https://groups.google.com/d/msgid/golang-nuts/e55ee408-fdf3-4472-9e87-84647197ed73n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CADLW2vzTc3RLAEhD%3DesVodJDCG_v%2BYVFnt5_pE8pOtBhstADGQ%40mail.gmail.com.