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
  • #18330

Closed (moved)
Open
Opened Feb 17, 2016 by Georg Koppen@gk

Tor Launcher only accepts HEXDIGIT passwords for controller

We currently give the advice to double quote the password for the Tor controller in the start-tor-browser script which seems to be a good thing given the trouble with quoting correctly. But this does not work (I wonder if it actually ever worked). The problem is that Tor Launcher is expecting a HEXDIGIT password. Using deadbeef is fine but

password[i] = parseInt(aHexPassword.substr(i * 2, 2), 16);

does not like things like test or '"test"' and is e.g. reporting for the former NaN, NaN which breaks the hashed control password option (the argument aHexPassword is spoiling the bug hunt a bit but I was not affected by it :) ). That in turn breaks the authentication and Tor Browser won't start.

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