Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 968
    • Issues 968
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 31
    • Merge requests 31
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #15743
Closed
Open
Issue created Jul 19, 2018 by sajolida@sajolidaMaintainer

Too much log when using obfs4 in Tails

Originally created by @sajolida on #15743 (Redmine)

From Cybelle’s report: https://lists.torproject.org/pipermail/tor-project/2018-July/001871.html

Tails 3.7 Debug or a high level of logging still present in /var/log/tor/log - when using obf4 (or whatever) bridges. This is a reminder that this problem continues to exist in Tails 3.7 (and several versions prior). The logging is crazy and consumes several MB per session. “warn Your log may contain sensitive information - you’re logging more than ”notice". Don’t log unless it serves an important reason. Overwrite the log afterwards.

I think we should check that…

Feature Branch: bugfix/15743-tor-log-level-with-bridges+force-all-tests

Related issues

  • Related to #15548 (closed)
  • Blocks tails/accounting#15507
Edited May 15, 2020 by sajolida
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking