Closed
Description
Current Assembly Policy establish general guidelines for inclusion of assembly implementations. However there is some confusion about it application to crypto.
I think we should clarify the following questions:
- Are assembly implementations of new (to go) modes/hashes/block-ciphers allowed at all?
- If they are allowed, we should have a list of deprecated stuff, that is intended to be slow e. g. rc4.
- Are there any additional requirements for testing crypto asm?
- Can I (or anyone without great background in crypto) +2 straightforward cases e. g. https://go-review.googlesource.com/c/go/+/125316 ?
- If we are not going to accept new assembly implemntaions, than we must do something with CLs sent before creation of assembly policy, that are still in review, e. g. https://go-review.googlesource.com/c/go/+/109135