Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 934
    • Issues 934
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 18
    • Merge requests 18
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • 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
  • #5769

Closed
Open
Created Jul 18, 2013 by import-from-Redmine@import-from-Redmine5 of 5 tasks completed5/5 tasks

Applications audit

Originally created by Tails on #5769 (Redmine)

Any included networked application needs to be analyzed for possible information leakages at the protocol level, e.g. if email clients leak the real IP address through the EHLO/HELO request etc.

This could be limited to applications whose protocol allows for such leakages.

General issues

The "claws with torsocks leaks hostname; bug was fixed, but the fact that torsocks behaves worse than tsocks in this respect is worrying and should be investigated further. Perhaps other applications using torify are also affected?

Per-software sub-pages:

Resources

  • iSECPartners’ LibTech-Auditing-Cheatsheet

Subtasks

  • #6117 (closed)
  • #6118 (closed)
  • #6115 (closed)
  • #6121 (closed)
  • #6119 (closed)
Edited Oct 18, 2020 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking