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

Closed
Open
Opened Feb 06, 2005 by Steven Murdoch@sjm217

Makefile doesn't use passive FTP

In the Makefile download-openssl target, wget (and possibly curl) use active FTP by default and fail if behind a NAT box, or in my case a paranoid firewall. Is there any reason not to use passive FTP? For wget the "--passive-ftp" switch will do this, I don't know about curl. Another option would be to use HTTP, which would get past even more paranoid HTTP-only firewalls, and those who are required to use a HTTP proxy.

[Automatically added by flyspray2trac: Operating System: All]

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