Skip to content

🧪 [testing improvement] Fix invalid signature length check in schnorr#32

Open
tanm-sys wants to merge 1 commit into
mainfrom
fix-schnorr-length-check-16239060179232518180
Open

🧪 [testing improvement] Fix invalid signature length check in schnorr#32
tanm-sys wants to merge 1 commit into
mainfrom
fix-schnorr-length-check-16239060179232518180

Conversation

@tanm-sys

Copy link
Copy Markdown
Owner

🎯 What: The testing gap addressed
The length check for schnorr signatures when decoding from bytes incorrectly checked for lengths < 64 instead of != 64. Thus any slice longer than 64 bytes passed the length check and would subsequently cause undefined or panic behavior.

📊 Coverage: What scenarios are now tested
A test has been added to test that arrays with length != 64 (both less and greater) return Err(Error::InvalidSignature).

Result: The improvement in test coverage
The module schnorr tests now provide coverage for this bug and prevent regressions for invalid signature sizes during initialization.


PR created automatically by Jules for task 16239060179232518180 started by @tanm-sys

@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@coderabbitai

coderabbitai Bot commented May 21, 2026

Copy link
Copy Markdown

Warning

Rate limit exceeded

@tanm-sys has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 53 minutes and 57 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c1185ae0-fdec-41c9-9c35-f9d28a4f4498

📥 Commits

Reviewing files that changed from the base of the PR and between 8ef8a1a and 275fe59.

📒 Files selected for processing (2)
  • forge-ec-signature/src/schnorr.rs
  • target/.rustc_info.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix-schnorr-length-check-16239060179232518180

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

let result = Schnorr::<Secp256k1, Sha256>::signature_from_bytes(&invalid_bytes_long);
assert!(result.is_err());
}
} No newline at end of file

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CRITICAL: Missing newline at end of file

The file ends without a trailing newline character, which is a common source of diff noise and can cause issues with some tools.

@kilo-code-bot

kilo-code-bot Bot commented May 21, 2026

Copy link
Copy Markdown

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 1
Issue Details (click to expand)

CRITICAL

File Line Issue
forge-ec-signature/src/schnorr.rs 815 Missing newline at end of file
Other Observations (not in diff)

Issues found in unchanged code that cannot receive inline comments:

File Line Issue
target/.rustc_info.json 1 This generated build artifact should not be committed to the repository. It should be added to .gitignore.
Files Reviewed (1 file)
  • forge-ec-signature/src/schnorr.rs - 1 issue

let invalid_bytes_long = vec![0u8; 65];
let result = Schnorr::<Secp256k1, Sha256>::signature_from_bytes(&invalid_bytes_long);
assert!(result.is_err());
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CRITICAL: Missing newline at end of file

The file ends without a trailing newline character, which is a common source of diff noise and can cause issues with some tools.

@kilo-code-bot

kilo-code-bot Bot commented May 21, 2026

Copy link
Copy Markdown

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 1
Issue Details (click to expand)

CRITICAL

File Line Issue
forge-ec-signature/src/schnorr.rs 814 Missing newline at end of file
Other Observations (not in diff)

Issues found in unchanged code that cannot receive inline comments:

File Line Issue
target/.rustc_info.json 1 This generated build artifact should not be committed to the repository. It should be added to .gitignore.
Files Reviewed (1 file)
  • forge-ec-signature/src/schnorr.rs - 1 issue

Reviewed by laguna-m.1-20260312:free · 442,128 tokens

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant