Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(crypto/ledger): Improve error message when deriving paths #22116

Merged
merged 2 commits into from
Oct 3, 2024

Conversation

raynaudoe
Copy link
Contributor

@raynaudoe raynaudoe commented Oct 3, 2024

Description

Closes: #19687

Improve error message when trying to derive paths with index > 100.


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title, you can find examples of the prefixes below:
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • New Features

    • Introduced enhanced error handling for public key address retrieval to improve security.
    • Added a check to prevent the use of address indices greater than 100, ensuring safer derivation paths.
    • New module x/validate added to enhance functionality.
    • Support for nested messages implemented, improving message handling.
  • Improvements

    • Enhanced error messaging for better user understanding.
  • Bug Fixes

    • Various updates documented for the baseapp, crypto/keyring, and x/auth modules.

@raynaudoe raynaudoe requested review from JulianToledano and a team as code owners October 3, 2024 18:34
Copy link
Contributor

coderabbitai bot commented Oct 3, 2024

📝 Walkthrough
📝 Walkthrough

Walkthrough

The changes introduce a new error handling mechanism in the getPubKeyAddrSafe function of the crypto/ledger/ledger_secp256k1.go file. A conditional check is added to ensure that the AddressIndex in the path parameter does not exceed 100. If it does, the function returns an error message indicating that indices greater than 100 are not allowed for security reasons. This adjustment aims to enhance error reporting without altering the existing functionality of the code.

Changes

File Change Summary
crypto/ledger/ledger_secp256k1.go Added error handling for AddressIndex exceeding 100 in getPubKeyAddrSafe.
CHANGELOG.md Updated changelog format and content, added new features and bug fixes.

Assessment against linked issues

Objective Addressed Explanation
Improve error message for index > 100 (19687)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

This comment has been minimized.

@raynaudoe raynaudoe added the backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release label Oct 3, 2024
@raynaudoe raynaudoe changed the title fix(ledger): Improve error message when deriving paths fix(crypto/ledger): Improve error message when deriving paths Oct 3, 2024
Copy link
Member

@julienrbrt julienrbrt left a comment

Choose a reason for hiding this comment

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

lgtm! An improvement changelog entry would be nice

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
crypto/ledger/ledger_secp256k1.go (1)

344-349: Approve changes with a minor suggestion for improvement

The changes effectively address the PR objective by improving the error message when deriving paths with an index greater than 100. The new error message is informative and provides context about the security measure.

Consider breaking the long error message into multiple lines for better readability:

return nil, "", fmt.Errorf("%w: cannot derive paths where index > 100: %s\n"+
    "This is a security measure to avoid very hard to find derivation paths introduced by a possible attacker.\n"+
    "You can disable this by setting expert mode in your ledger device. Do this at your own risk", 
    err, path)

This formatting will make the error message easier to read in the code while maintaining the same output.

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 69914dc and 3ef79c1.

📒 Files selected for processing (1)
  • crypto/ledger/ledger_secp256k1.go (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
crypto/ledger/ledger_secp256k1.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
CHANGELOG.md (1)

Line range hint 4-6: Address TODO comment and add tests

The TODO comment indicates that tests should be added for this function. It's important to implement these tests to ensure the function works as expected, especially given its mathematical operations.

Consider adding unit tests for various input scenarios, including edge cases like very large numbers or negative inputs.

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 3ef79c1 and 737dae7.

📒 Files selected for processing (1)
  • CHANGELOG.md (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
CHANGELOG.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

@raynaudoe raynaudoe added this pull request to the merge queue Oct 3, 2024
Merged via the queue into main with commit 5bed965 Oct 3, 2024
74 of 76 checks passed
@raynaudoe raynaudoe deleted the eze/fix_ledger_index_err branch October 3, 2024 19:44
mergify bot pushed a commit that referenced this pull request Oct 3, 2024
(cherry picked from commit 5bed965)

# Conflicts:
#	CHANGELOG.md
julienrbrt added a commit that referenced this pull request Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: Improve error message when making a ledger key with index > 100
3 participants