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

Closed (moved)
Open
Opened Apr 14, 2018 by Trac@tracbot

Infinite restart loop when daemon crashes

On Ubuntu, using Tor from the official PPA, when the Tor daemon crashes (im my case because of this bug https://trac.torproject.org/projects/tor/ticket/23693), it is automatically restarted.

As a result Tor uses 100% CPU continuously because of its hopeless start->crash->start->crash... behavior.

A better behavior could be to detect the crash (SIGSEV, SIGABRT...) from the process return code and do not restart in that case.

The crash-restart loop behavior can also be dangerous security wise, because for example exploits against ASLR have a framework to do brute force attacks if the process automatically restarts.

I could not understand where this behavior comes from in the code, because the systemd service file in /lib/systemd/system/tor.service seem to be empty.

Trac:
Username: tiejohg2sahth

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