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

Closed (moved)
Open
Opened Sep 17, 2019 by Trac@tracbot

MAPADDRESS control command

I'm using the control socket to execute MAPADDRESS commands. Since TorBrowser 8.5.5 (Linux64) with Tor 0.4.1.5 the behavior changed.

On TorBrowser 8.5.4 (Linux64) with Tor 0.4.0.5 the following command worked:

MAPADDRESS *.torproject.org=127.0.0.1 250 *.torproject.org=127.0.0.1

On TorBrowser 8.5.5 (Linux64) with Tor 0.4.1.5 the following happens:

MAPADDRESS *.torproject.org=127.0.0.1 512 syntax error: not enough arguments to mapaddress.

However, I found out that the following works:

MAPADDRESS foo *.torproject.org=127.0.0.1 250 *.torproject.org=127.0.0.1

I could not find any information about a change in the MAPADDRESS command specification.

Did the MAPADDRESS command change or may this be a bug in the command parsing?

Trac:
Username: kowenki

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