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: add sldev.cz domain into whitelist to allow for testing of on Suite upgrade flow #16895

Merged
merged 1 commit into from
Feb 10, 2025

Conversation

peter-sanderson
Copy link
Contributor

No description provided.

Copy link

coderabbitai bot commented Feb 8, 2025

Walkthrough

The change modifies the application’s domain configuration by adding a new entry to the allowedDomains list in the packages/suite-desktop-core/src/config.ts file. The domain 'sldev.cz' has been introduced, accompanied by a comment indicating that it is a test environment accessible only with a VPN. This update expands the set of domains that the application considers valid, which may influence network request handling and security policies within the application.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5d18877 and 91e4d65.

📒 Files selected for processing (1)
  • packages/suite-desktop-core/src/config.ts (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • packages/suite-desktop-core/src/config.ts
⏰ Context from checks skipped due to timeout of 90000ms (8)
  • GitHub Check: run-desktop-tests (@group=wallet, trezor-user-env-unix bitcoin-regtest)
  • GitHub Check: run-desktop-tests (@group=other, trezor-user-env-unix)
  • GitHub Check: run-desktop-tests (@group=settings, trezor-user-env-unix bitcoin-regtest)
  • GitHub Check: run-desktop-tests (@group=device-management, trezor-user-env-unix)
  • GitHub Check: run-desktop-tests (@group=suite, trezor-user-env-unix)
  • GitHub Check: build-web
  • GitHub Check: Analyze with CodeQL (javascript)
  • GitHub Check: Setup and Cache Dependencies

🪧 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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

Copy link

@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

🧹 Nitpick comments (1)
packages/suite-desktop-core/src/config.ts (1)

16-16: Consider documenting VPN requirements more prominently.

While the inline comment is helpful, consider documenting the VPN requirements and test environment details more prominently in the project's documentation to ensure all developers are aware of the access requirements.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cf806ff and 5d18877.

📒 Files selected for processing (1)
  • packages/suite-desktop-core/src/config.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (8)
  • GitHub Check: run-desktop-tests (@group=wallet, trezor-user-env-unix bitcoin-regtest)
  • GitHub Check: run-desktop-tests (@group=other, trezor-user-env-unix)
  • GitHub Check: run-desktop-tests (@group=settings, trezor-user-env-unix bitcoin-regtest)
  • GitHub Check: run-desktop-tests (@group=device-management, trezor-user-env-unix)
  • GitHub Check: run-desktop-tests (@group=suite, trezor-user-env-unix)
  • GitHub Check: Setup and Cache Dependencies
  • GitHub Check: build-web
  • GitHub Check: Analyze with CodeQL (javascript)
🔇 Additional comments (1)
packages/suite-desktop-core/src/config.ts (1)

16-16: Verify VPN access restrictions for the test domain.

The comment indicates this is a VPN-protected test environment. Please ensure:

  1. The VPN requirement is properly enforced
  2. The domain is not accessible from public networks

Let's verify the domain's accessibility:

✅ Verification successful

🏁 Script executed:

#!/bin/bash
# Description: Check if the domain is accessible without VPN
# Expected: Connection timeout or refused, indicating VPN requirement

curl -I --connect-timeout 5 https://sldev.cz

Length of output: 326


Domain VPN Restriction Confirmed

The output shows that attempting to access https://sldev.cz without VPN results in a DNS resolution error ("Could not resolve host: sldev.cz"), which confirms the domain is not publicly accessible. This behavior aligns with the intended security configuration for a VPN-protected test environment.

• Verify that the DNS/VPN configuration is correctly set up so that the domain becomes resolvable only when connected to the VPN.
• Consider enhancing internal documentation to more prominently state the VPN dependency for accessing this test domain.

@peter-sanderson peter-sanderson merged commit 763db76 into develop Feb 10, 2025
25 checks passed
@peter-sanderson peter-sanderson deleted the add-sldev-to-whitelist branch February 10, 2025 10:16
@bosomt
Copy link
Contributor

bosomt commented Feb 11, 2025

QA OK

tested on macARM /it will be retested on other platforms and in any case of problem it will be reported/

Info:

  • Suite version: desktop 35.2.1 (4b92a09)
  • Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) TrezorSuite/35.2.1 Chrome/128.0.6613.186 Electron/32.2.6 Safari/537.36
  • OS: MacIntel
  • Screen: 1470x956
  • Device: Trezor T2T1 2.8.8 regular (revision 592590cf66a9b62dfeee7e4d2afb6e01005e5b2c)
  • Transport: BridgeTransport 3.0.0-bundled.35.2.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Approved
Development

Successfully merging this pull request may close these issues.

3 participants