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

Closed (moved)
(moved)
Open
Created Nov 09, 2016 by Roger Dingledine@arma

obfs4proxy package on deb.tp.o is out of date?

http://deb.torproject.org/torproject.org/dists/obfs4proxy/main/binary-amd64/Packages makes it look like we're shipping obfs4proxy 0.0.4 on deb.torproject.org.

Whereas Debian sid, and apparently ubuntu 16.04, have obfs4proxy 0.0.6: https://packages.debian.org/sid/obfs4proxy

Are we not keeping our deb repo up-to-date?

It doesn't seem reasonable to think that we're shipping jessie's stable, because that looks to be version 0.0.3: https://packages.debian.org/search?keywords=obfs4proxy

Moritz points out that our current stackexchange answer suggests to use the Tor obs4proxy repo: https://tor.stackexchange.com/questions/6370/how-to-run-an-obfs4-bridge/6371

Are we at the point where we should stop maintaining our own? Or did that ship sail when we started doing it?

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