Golang ECDSA Sign implementation is now safe from bad entropy sources! (But it’s still randomized, unlike RFC6979)https://github.com/golang/go/commit/a8049f58f9e3336554da1b0a4f8ea3b9c5cd669c …
-
-
@AndreaBarisani I’ll give you my favorite kind of advice: unless you know why not, use Go. Go is a better starting point for most projects.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@AndreaBarisani You’ll know it if you hit one of the reasons not to use Go (extreme perf, certain constant time impl) -
@FiloSottile my only concern is not being able to offload to hw crypto, but that might not be a deal breaker for several reasons -
@AndreaBarisani example use case? -
@FiloSottile but offloading gives advantage over pure CPU only on certain conditions, might not be worth at all for the app -
@AndreaBarisani if for offloading you mean AES-NI, I might be wrong but I think Go has ASM for AES :) -
@FiloSottile that is different, I mean hardware co-processor typically used via cryptodev or af_alg. We don't have aes-ni.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.