Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
T
Tor
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,078
    • Issues 1,078
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 24
    • Merge Requests 24
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

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.

  • The Tor Project
  • Core
  • Tor
  • Issues
  • #25477

Closed
Open
Created Mar 13, 2018 by George Kadianakis@asnOwner

Stop warning users about bug #21018

While working on legacy/trac#14389 (moved) we figured out that when a Tor client connects to an onion service with authorization without the proper authorization client config (or non-existent auth config), Tor will throw out 6 warnings like this:

 [warn] Failed to parse introduction points. Either the service has published a corrupt descriptor or you have provided invalid authorization data, or (maybe!) the server is deliberately serving broken data in an attempt to crash you with bug 21018.

We should consider removing the alarmist warn about bug legacy/trac#21018 (moved) at some point, and maybe that point is now, since it might freak out users for no reason and there is no way for us to learn whether the attack took place.

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