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

Closed (moved)
Open
Opened Nov 10, 2017 by David Goulet@dgoulet🐋

control: HS_DESC event failed upload sends back the wrong Action

When a descriptor upload fails, tor sends on the control port a UPLOAD_FAILED event where in fact it should be sending a FAILED event as the action with the reason: UPLOAD_REJECTED or UNEXPECTED.

The control_event_hs_descriptor_upload_failed() is the offending function.

The control spec does not specify at all the Action=UPLOAD_FAILED nor Stem for instance knows about it so this is a problem on tor side.

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