| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
EC_KEY_set_public_key_affine_coordinates() and EC_KEY_get0_public_key()
than using EC_POINT_set_affine_coordinates_GFp() directly.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
against its ANSI equivalent prime256v1 (compare RFC 4492, Appendix A).
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
look into
|
| |
|
| |
|
| |
|
|
|
|
| |
acceptable cases.
|
|
|
|
| |
identifying the important failures while auditing.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
single AEAD types. Will be used in upcoming commits.
|
| |
|
| |
|
|
|
|
|
| |
is the magic string that is recognized by my test framework.
OK tb@
|
| |
|
| |
|
|
|
|
| |
two noisy INFO and reorder things a bit.
|
|
|
|
| |
will be fixed with the next commit to libcrypto.
|
| |
|
| |
|
| |
|
|
|
|
| |
Suggested by jsing
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
pointed out by gofmt (thanks anton)
|
| |
|