This repository has been archived by the owner on Dec 18, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 103
Add test and fix for non-canonical point at infinity #157
Closed
Closed
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,7 @@ | ||
use ark_ec::{short_weierstrass::Affine, AffineRepr}; | ||
use ark_ff::{BigInteger384, PrimeField}; | ||
use ark_serialize::SerializationError; | ||
use ark_std::Zero; | ||
|
||
use crate::{g1::Config as G1Config, g2::Config as G2Config, Fq, Fq2, G1Affine, G2Affine}; | ||
|
||
|
@@ -14,6 +15,7 @@ pub struct EncodingFlags { | |
} | ||
|
||
impl EncodingFlags { | ||
/// Fetches the flags from the byte-string | ||
pub fn get_flags(bytes: &[u8]) -> Self { | ||
let compression_flag_set = (bytes[0] >> 7) & 1; | ||
let infinity_flag_set = (bytes[0] >> 6) & 1; | ||
|
@@ -25,6 +27,8 @@ impl EncodingFlags { | |
is_lexographically_largest: sort_flag_set == 1, | ||
} | ||
} | ||
|
||
/// Encodes the flags into the byte-string | ||
pub fn encode_flags(&self, bytes: &mut [u8]) { | ||
if self.is_compressed { | ||
bytes[0] |= 1 << 7; | ||
|
@@ -38,6 +42,13 @@ impl EncodingFlags { | |
bytes[0] |= 1 << 5; | ||
} | ||
} | ||
|
||
/// Removes the flags from the byte-string. | ||
/// | ||
/// This reverses the effects of `encode_flags`. | ||
pub fn remove_flags(bytes: &mut [u8]) { | ||
bytes[0] &= 0b0001_1111; | ||
} | ||
} | ||
|
||
pub(crate) fn deserialize_fq(bytes: [u8; 48]) -> Option<Fq> { | ||
|
@@ -81,8 +92,7 @@ pub(crate) fn read_fq_with_offset( | |
tmp.copy_from_slice(&bytes[offset * G1_SERIALIZED_SIZE..G1_SERIALIZED_SIZE * (offset + 1)]); | ||
|
||
if mask { | ||
// Mask away the flag bits | ||
tmp[0] &= 0b0001_1111; | ||
EncodingFlags::remove_flags(&mut tmp); | ||
} | ||
deserialize_fq(tmp).ok_or(SerializationError::InvalidData) | ||
} | ||
|
@@ -99,18 +109,23 @@ pub(crate) fn read_g1_compressed<R: ark_serialize::Read>( | |
// Obtain the three flags from the start of the byte sequence | ||
let flags = EncodingFlags::get_flags(&bytes[..]); | ||
|
||
// we expect to be deserializing a compressed point | ||
// We expect to be deserializing a compressed point | ||
if !flags.is_compressed { | ||
return Err(SerializationError::UnexpectedFlags); | ||
} | ||
|
||
// Attempt to obtain the x-coordinate | ||
let x = read_fq_with_offset(&bytes, 0, true)?; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should we make this a byte-based check? i.e. directly on the bytes that we've read? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good catch, I've PRed to @kevaundray's fork, if not merged there soon I'll open a PR directly here. |
||
|
||
if flags.is_infinity { | ||
// Check that the `x` co-ordinate was `0` | ||
if !x.is_zero() { | ||
return Err(SerializationError::InvalidData); | ||
} | ||
|
||
return Ok(G1Affine::zero()); | ||
} | ||
|
||
// Attempt to obtain the x-coordinate | ||
let x = read_fq_with_offset(&bytes, 0, true)?; | ||
|
||
let p = G1Affine::get_point_from_x_unchecked(x, flags.is_lexographically_largest) | ||
.ok_or(SerializationError::InvalidData)?; | ||
|
||
|
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think some extra validation here is needed to catch another, more subtle class of non-canonical infinity point encodings: some flag combinations are nonsensical. Here's a failing test to show you what I mean: