sec1: Elliptic-Curve-Point-to-Octet-String encoding
#45
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds support for encoding elliptic curve points according to the following algorithms defined in SEC1: - `Elliptic-Curve-Point-to-Octet-String` - `Octet-String-to-Elliptic-Curve-Point` These encodings use a tag byte (0x02/0x03 for compressed, 0x04 for uncompressed) followed by one or two big endian-serialized field elements representing the x/y coordinates of a curve point. This is an extraction of the implementation from the `elliptic-curve` crate, decoupled from the types in that crate and thus generally useful for any crate which wishes to implement SEC1 support.
tarcieri
added a commit
to RustCrypto/traits
that referenced
this pull request
Sep 19, 2021
The `EncodedPoint` type was extracted to the `sec1` crate in: RustCrypto/formats#45 This switches the `elliptic-curve` to using the newly extracted implementation. This was a bit tricky/invasive as now `EncodedPoint` now only knows a size and not the rest of the details of the curve. APIs that were previously heavily leveraging `EncodedPoint` should probably switch to the `PublicKey` type instead unless they are specifically intending to work with SEC1-encoded points.
tarcieri
added a commit
to RustCrypto/traits
that referenced
this pull request
Sep 19, 2021
The `EncodedPoint` type was extracted to the `sec1` crate in: RustCrypto/formats#45 This switches the `elliptic-curve` to using the newly extracted implementation. This was a bit tricky/invasive as now `EncodedPoint` now only knows a size and not the rest of the details of the curve. APIs that were previously heavily leveraging `EncodedPoint` should probably switch to the `PublicKey` type instead unless they are specifically intending to work with SEC1-encoded points.
tarcieri
added a commit
to RustCrypto/traits
that referenced
this pull request
Sep 19, 2021
The `EncodedPoint` type was extracted to the `sec1` crate in: RustCrypto/formats#45 This switches the `elliptic-curve` to using the newly extracted implementation. This was a bit tricky/invasive as now `EncodedPoint` now only knows a size and not the rest of the details of the curve. APIs that were previously heavily leveraging `EncodedPoint` should probably switch to the `PublicKey` type instead unless they are specifically intending to work with SEC1-encoded points.
tarcieri
added a commit
to RustCrypto/traits
that referenced
this pull request
Sep 19, 2021
The `EncodedPoint` type was extracted to the `sec1` crate in: RustCrypto/formats#45 This switches the `elliptic-curve` to using the newly extracted implementation. This was a bit tricky/invasive as now `EncodedPoint` now only knows a size and not the rest of the details of the curve. APIs that were previously heavily leveraging `EncodedPoint` should probably switch to the `PublicKey` type instead unless they are specifically intending to work with SEC1-encoded points.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds support for encoding elliptic curve points according to the following algorithms defined in SEC1:
Elliptic-Curve-Point-to-Octet-StringOctet-String-to-Elliptic-Curve-PointThese encodings use a tag byte (0x02/0x03 for compressed, 0x04 for uncompressed) followed by one or two big endian-serialized field elements representing the x/y coordinates of a curve point.
This is an extraction of the implementation from the
elliptic-curvecrate, decoupled from the types in that crate and thus generally useful for any crate which wishes to implement SEC1 support.