Evgeniy Kulikov
5bcaeeca4e
Merge pull request #7 from nspcc-dev/NEOFS_CRYPTO-4_Use_sha512_instead_of_sha256
...
Use SHA512 instead of SHA256
2019-11-12 16:42:33 +03:00
Evgeniy Kulikov
21d0864dae
Merge pull request #6 from nspcc-dev/NEOFS_CRYPTO-4_Change_func_Verify_signature
...
- Before `func Verify*(pub *ecdsa.PublicKey, sig, msg []byte) error`
- After `func Verify*(pub *ecdsa.PublicKey, msg, sig []byte) error`
- Update tests and replace `hash` with `sign` for signatures
Fix issue #5
2019-11-12 16:41:17 +03:00
Evgeniy Kulikov
943bb90aec
Use SHA512 instead of SHA256
...
Fix issue #4
2019-11-12 16:00:27 +03:00
Evgeniy Kulikov
fc6fd40f5e
Change func Verify signature
...
- Before `func Verify*(pub *ecdsa.PublicKey, sig, msg []byte) error`
- After `func Verify*(pub *ecdsa.PublicKey, msg, sig []byte) error`
- Update tests and replace `hash` with `sign` for signatures
Fix issue #5
2019-11-12 15:52:13 +03:00
Evgeniy Kulikov
bd754c2f99
Merge pull request #3 from nspcc-dev/fix-naming
...
Use consistent parameter names for Sign and Verify functions
2019-11-12 15:28:54 +03:00
alexvanin
8fa65a0afc
Use consistent parameter names for Sign and Verify functions
...
It may be misleading when verify function takes signature as a hash
parameter. This commit suggested to use rfc6979 original naming
for the parameters:
- `msg` as the message to sign,
- `sig` as the signature of message.
All hashing operations are encapsulated inside of the Sign
and Verify functions.
Also there are comment fixes and re-usage of `hashBytes()` in rfc6979.
2019-11-12 14:52:23 +03:00
Evgeniy Kulikov
40d65daa2e
Merge pull request #1 from nspcc-dev/use_stdlib_formula_for_decompress_point
...
Refactor decompress Y point
2019-10-24 12:56:25 +03:00
Evgeniy Kulikov
e60428333c
Refactor decompress Y point
2019-10-23 14:05:04 +03:00
Evgeniy Kulikov
c21ef9ef81
initial
2019-10-22 17:40:05 +03:00
