Skip to content

🔒 Enforce SSL verification across all proxy links - #9

Open
maattyi wants to merge 1 commit into
mainfrom
fix-ssl-verification-enforcement-13271791097324461944
Open

🔒 Enforce SSL verification across all proxy links#9
maattyi wants to merge 1 commit into
mainfrom
fix-ssl-verification-enforcement-13271791097324461944

Conversation

@maattyi

@maattyi maattyi commented May 1, 2026

Copy link
Copy Markdown
Owner

🔒 Security Fix: Enforce SSL Verification

🎯 What:

The vulnerability allowed users (or a malicious configuration) to disable SSL certificate verification and hostname checking. This insecure state made the proxy susceptible to MITM attacks, which could lead to the theft of sensitive data such as the Auth Key.

⚠️ Risk:

If left unfixed, an attacker positioned between the proxy and the relay (e.g., on the local network or ISP level) could intercept and potentially modify the traffic, compromising the user's connection and credentials.

🛡️ Solution:

I have strictly enforced SSL verification project-wide by:

  1. Forcing Secure Settings: Updating DomainFronter to override any insecure verify_ssl=False configuration with a warning.
  2. Removing Vulnerable Code: Deleting blocks in domain_fronter.py, proxy_server.py, and h2_transport.py that explicitly disabled SSL security measures.
  3. Defaulting to Safety: Ensuring all outgoing TLS connections use Python's secure default SSL context.

Verification was performed using a local mock server with a self-signed certificate, confirming that the proxy now correctly rejects untrusted connections even when configured to bypass verification.


PR created automatically by Jules for task 13271791097324461944 started by @maattyi

This commit addresses a security vulnerability where SSL certificate verification could be disabled, exposing users to Man-in-the-Middle (MITM) attacks.

- Modified `DomainFronter` to enforce `verify_ssl=True` and log a security warning if it was set to `False`.
- Removed all manual overrides that set `ssl.CERT_NONE` and `check_hostname = False` in `domain_fronter.py`, `proxy_server.py`, and `h2_transport.py`.
- Ensured consistent use of `ssl.create_default_context()` for all outbound TLS connections.
- Added ALPN advertisement for `http/1.1` in the proxy's SNI-rewrite tunnel to maintain compatibility.

Co-authored-by: maattyi <228237318+maattyi@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown

👋 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.

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