Andreas Auernhammer

As far as I can see the micro-ecc library uses the NIST curves secp160r1 - secp256r1, and secp256k1. The NIST curves P224 - P521 are directly supported - see the...

golang/go#19513

@Inkeliz Thank you for the hint - I'm aware of this, I've implemented the linked package 😃 See [BLAKE2Xb](https://go-review.googlesource.com/c/crypto/+/38055) , [BLAKE2Xs](https://go-review.googlesource.com/c/crypto/+/38054)

@ThrawnCA That may be the case. I'm not sure whether it's okay to expose an ABE rule set as part of the policy.json and incrementally build a UI for ABE...

@musonius For the described use-case that would be an option, too. E.g. a button with the semantics: `rule apply only on this domain`. For example setting `Domain-A` as trusted on...

I was not able to get this to work with e.g. `play` until I fixed the code locally. Kept failing with `invalid region error` returned from the S3 server...

Yes, a `fips` build tag is needed. FIPS / boringcrypto requires that a specific implementation of SHA-256 is used. A "custom" SHA-256 implementation (like SHA256-simd) will not work.

Hm interesting. For me it starts quite slow (`~200 KiB/s`) but after a 15/20s or so it becomes quite fast `> 10 MiB/s`. After about 15% it starts speeding up..

I've created an issue at the google repo, too. The argument for deleting may be correct (formally ?!) but does not reflect the actual situation. HighwayHash is used by multple...

> @aead once this is merged. Can we simply force merge this to downstream mineos? Since there are conflicts in cherry picking want to make sure that is perfectly fine....