compatibility with other crypto libraries
- Dominant language
- C
- Stars
- 296
- Forks
- 70
- PR merge metrics
- No merged PRs in 30d
Description
using K-163, i've generated a public key from the private key [0, 1, 2, ...] .... the results do NOT match the public key i generate using nodejs (which itself uses openssl, i believe)....
i've seen other issues suggesting that there may not (yet) be compatibility with other crypto libraries....
said another way, are there standard test vectors which you've used??? do you have some "expected output for this particular input" tests????
Contributor guide
No contributing guide indexed for this repository
Research direction
No source files or tests are named. Start by reproducing the K-163 public-key calculation from the private key [0, 1, 2, ...] and compare it with the Node.js/OpenSSL result, then look for existing standard test vectors or expected-output tests. Done means identifying whether the mismatch is expected and documenting or testing the compatible result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, node.js
- Domain
- cryptography
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100