Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tor-launcher
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • tor-launcher
  • Issues
  • #18330

Closed
Open
Created Feb 17, 2016 by Georg Koppen@gkDeveloper

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 an admin enable hashed storage. More information
Assignee
Assign to
Time tracking