Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #19449

Closed (moved)
(moved)
Open
Created Jun 19, 2016 by Roger Dingledine@arma

Remove --disable-transparent configure option?

Right now --enable-transparent is the default in ./configure.

I don't know of anyplace that disables it.

And that means that if there's any place that fails to build with it enabled, we would have heard about it, right?

So, the only possible remaining reason to disable it is if we don't want that extra code in Tor, for security reasons? Are there libraries that we choose not to link if it's disabled? Or is it just a couple of lines of code that we run or don't run?

(I noticed this option again while noticing that FreeBSD's Tor port ( https://trac.torproject.org/projects/tor/attachment/ticket/7734/FreeBSD_Tor_port_config.png ) gives the user the option of choosing --disable-transparent, along with other things like --enable-bufferevents and --enable-instrument-downloads that are distractions at best and downright dangerous sometimes.)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking