Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #26306

Closed (moved)
Open
Opened Jun 04, 2018 by Trac@tracbot

HTTPS proxy doesn't use TLS

Following configuration in GUI

HTTP/HTTPS proxy
Address: example.com (https://example.com fails to parse)
Port: 443
Credentials: username:password

generates torrc with:

HTTPSProxy example.com:443
HTTPSAuthenticator username:password

When configured this way, Tor sends CONNECT request with my credentials over plaintext HTTP to port :443.

HTTPSProxy should be able to use HTTPS for proxying. HTTPS proxies are supported in Firefox, and could be configured via an extension, or a PAC file (which could be inlined in settings without using an actual file):

function FindProxyForURL(url, host) {
	if (host === "127.0.0.1")
		return "DIRECT";
	return "HTTPS example.com:443";
}

Trac:
Username: sf

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#26306