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 …
-
-
Replying to @FiloSottile
@FiloSottile I am tempted to use pure go crypto instead of openssl and gnupg for USB armory crypto frontend web app, what do you think?2 replies 0 retweets 1 like -
Replying to @AndreaBarisani
@AndreaBarisani You’ll know it if you hit one of the reasons not to use Go (extreme perf, certain constant time impl)1 reply 0 retweets 0 likes -
Replying to @FiloSottile
@FiloSottile my only concern is not being able to offload to hw crypto, but that might not be a deal breaker for several reasons1 reply 0 retweets 1 like -
-
Replying to @FiloSottile
@FiloSottile but offloading gives advantage over pure CPU only on certain conditions, might not be worth at all for the app1 reply 0 retweets 0 likes -
Replying to @AndreaBarisani
@AndreaBarisani if for offloading you mean AES-NI, I might be wrong but I think Go has ASM for AES :)1 reply 0 retweets 0 likes
@FiloSottile that is different, I mean hardware co-processor typically used via cryptodev or af_alg. We don't have aes-ni.
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.