Skip to content

Feature: Add section about Cryptomator desktop network settings #66

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

Merged
merged 2 commits into from
Feb 3, 2025

Conversation

infeo
Copy link
Member

@infeo infeo commented Jan 28, 2025

grafik

@infeo infeo requested a review from SailReal January 28, 2025 17:44
@infeo infeo self-assigned this Jan 28, 2025
Copy link

coderabbitai bot commented Jan 28, 2025

Walkthrough

The pull request introduces comprehensive documentation updates for Cryptomator, focusing on network-related configurations and the introduction of Cryptomator Hub. A new section titled "Network Settings" is added to the source/desktop/network.rst file, detailing network requirements, trust certificate management, and proxy server settings. It specifies that Cryptomator generally operates without a network connection but utilizes HTTPS connections for optional features like update checks and unlocking Hub vaults. Additionally, a new section header for "Cryptomator Hub" is included in the documentation, emphasizing its zero-knowledge key management capabilities and integration with identity management systems. The main index file is updated to incorporate the new network documentation.

Possibly related PRs

  • Added page for supported Cloud Services #60: The changes in the main PR regarding network settings and configurations for Cryptomator are related to the new page for supported Cloud Services, as both involve documentation that guides users on how to effectively use Cryptomator with various network and cloud service configurations.

Suggested reviewers

  • SailReal

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 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 (3)
source/desktop/network.rst (3)

8-8: Consider adding security context for TLS version.

The TLS requirement is correctly specified. Consider adding a brief note explaining why TLS 1.2 is the minimum requirement (e.g., "TLS 1.2 is required as earlier versions are considered insecure").


50-55: Enhance proxy configuration documentation.

Consider these improvements:

  1. Add example values (e.g., [1] could be proxy.example.com)
  2. Add a warning about security implications of proxy configuration
  3. Recommend backing up Cryptomator.cfg before editing

Example enhancement:

 java-options=-Dhttp.proxyHost=[1]
 java-options=-Dhttp.proxyPort=[2]
 java-options=-Dhttps.proxyHost=[1]
 java-options=-Dhttps.proxyPort=[2]
 java-options=-Dhttp.nonProxyHosts=localhost|127.0.0.1|cryptomator-vault|[3]
+
+Example:
+java-options=-Dhttp.proxyHost=proxy.example.com
+java-options=-Dhttp.proxyPort=8080
+java-options=-Dhttps.proxyHost=proxy.example.com
+java-options=-Dhttps.proxyPort=8080
+java-options=-Dhttp.nonProxyHosts=localhost|127.0.0.1|cryptomator-vault|internal.example.com
+
+Note: Before editing the configuration file, create a backup copy. Incorrect proxy settings
+might prevent Cryptomator from accessing the network.

56-56: Consider adding a troubleshooting section.

It would be helpful to add a section about common network-related issues and their solutions, such as:

  • Connection timeout errors
  • Certificate validation failures
  • Proxy authentication issues
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ff13750 and eefc95c.

📒 Files selected for processing (3)
  • source/desktop/network.rst (1 hunks)
  • source/hub/introduction.rst (1 hunks)
  • source/index.rst (1 hunks)
🔇 Additional comments (3)
source/hub/introduction.rst (1)

8-9: LGTM! Well-structured anchor reference.

The anchor reference is correctly formatted and placed, enabling proper cross-referencing throughout the documentation.

source/index.rst (1)

32-32: LGTM! Proper toctree entry.

The new network settings documentation is correctly integrated into the Desktop section's table of contents.

source/desktop/network.rst (1)

17-18: Clarify internal CA list details.

Consider specifying:

  1. Which common CAs are included in the internal list
  2. How users can view this list
  3. How the list is updated

Copy link
Member

@SailReal SailReal left a comment

Choose a reason for hiding this comment

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

Looks good, just a few minor things

@infeo infeo requested a review from SailReal January 29, 2025 13:00
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 (4)
source/desktop/network.rst (4)

10-10: Add details about TLS version support.

Consider adding information about the maximum supported TLS version and any deprecated versions for security-conscious users.

-All network connections to the internet are using HTTPS with at least TLS 1.2.
+All network connections to the internet are using HTTPS with TLS 1.2 or higher (up to TLS 1.3).

8-10: Clarify localhost connection behavior.

Based on previous discussions, it would be helpful to explicitly mention the behavior with localhost connections, especially for developers or users setting up local instances.

 If the network connection is present, it is used for optional features, i.e. update checks and searching the error database for solutions.
 The only exception is when unlocking :ref:`Cryptomator Hub <hub/introduction>` vaults, then a network connection to the hub server is required.
-All network connections to the internet are using HTTPS with at least TLS 1.2.
+All network connections to the internet are using HTTPS with at least TLS 1.2. Note that localhost connections (127.0.0.1) use HTTP, as HTTPS is not required for local connections.

33-33: Enhance the JEP reference with context.

The JEP 319 reference could be more helpful with a brief description of its relevance.

-.. [1] For more information about the location and contained certificates, see `JEP 319 <https://openjdk.org/jeps/319>`_.
+.. [1] For more information about the default trust store location and included root certificates in OpenJDK, see `JEP 319: Root Certificates <https://openjdk.org/jeps/319>`_.

62-66: Improve placeholder documentation and add validation steps.

The placeholders could be more descriptive, and it would be helpful to include steps for validating the proxy configuration.

-    java-options=-Dhttp.proxyHost=[1]
-    java-options=-Dhttp.proxyPort=[2]
-    java-options=-Dhttps.proxyHost=[1]
-    java-options=-Dhttps.proxyPort=[2]
-    java-options=-Dhttp.nonProxyHosts=localhost|127.0.0.1|cryptomator-vault|[3]
+    java-options=-Dhttp.proxyHost=<proxy-host>           # Example: proxy.example.com
+    java-options=-Dhttp.proxyPort=<proxy-port>           # Example: 8080
+    java-options=-Dhttps.proxyHost=<proxy-host>          # Same as http.proxyHost
+    java-options=-Dhttps.proxyPort=<proxy-port>          # Same as http.proxyPort
+    java-options=-Dhttp.nonProxyHosts=localhost|127.0.0.1|cryptomator-vault|<additional-hosts>   # Example: *.internal.net

After configuration, restart Cryptomator and verify the proxy settings by checking the connection to the update server or Hub.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between eefc95c and 0e8e335.

📒 Files selected for processing (1)
  • source/desktop/network.rst (1 hunks)
🔇 Additional comments (1)
source/desktop/network.rst (1)

22-23: Add information about default trust store certificates.

As mentioned in past reviews, it would be helpful to explain the source of certificates in the default trust store.

 | Linux   | | PKCS#12 file ``/etc/cryptomator/certs.p12``; If the file does not exist, the JDK default                                     |
-|         | | trust store is used. [1]_                                                                                    |
+|         | | trust store is used, which contains a curated list of common Certificate Authorities. [1]_                   |

@infeo infeo merged commit 628f7f7 into main Feb 3, 2025
2 checks passed
@infeo infeo deleted the feature/desktop-trust-store branch February 3, 2025 14:35
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.

Document which certificate trust store Cryptomator uses and how to adjust those
3 participants