[tor-bugs] #12903 [Pluggable transport]: Integrate obfs4proxy into the TBB bundle.
Tor Bug Tracker & Wiki
blackhole at torproject.org
Wed Aug 20 13:43:19 UTC 2014
#12903: Integrate obfs4proxy into the TBB bundle.
-------------------------------------+------------------------
Reporter: yawning | Owner: yawning
Type: task | Status: new
Priority: normal | Milestone:
Component: Pluggable transport | Version:
Resolution: | Keywords: obfs4, tbb
Actual Points: | Parent ID: #12130
Points: |
-------------------------------------+------------------------
Comment (by yawning):
Replying to [comment:1 dcf]:
> Replying to [ticket:12903 yawning]:
> > I was comfortable tagging obfs4proxy. Is there a way to say "use this
commit" for the other files?
>
> Just set VERIFY_TAGS=0. Cf. https://gitweb.torproject.org/user/dcf/tor-
browser-bundle.git/commitdiff/659a0d10206af8d1337b13967d32322f3693d996.
Ok. The nightly target currently fails to build due to things that I
assume aren't my fault (it fails when adding the TBB specific tor patches)
which is way before my added madness, so I'll try this with the alpha
target next.
Replying to [comment:2 gk]:
> Replying to [ticket:12903 yawning]:
> > * Is it ok to just mirror dependencies at
`people.tp.o/~yawning/mirrors/source`?
>
> I think the reason for doing so was, originally, just to be sure the
dependencies are really available when needed. Thus, if you have reasons
to fear/assume the infrastructure they are currently on is flaky etc. it
might indeed be better to host them on tpo infra.
A hah. The reason I put them in my ~ was that the gitian scripts
currently don't support pulling code in from mercurial and
`go.net`/`go.crypto` currently only live in hg on code.google.com. For
now I'll keep doing things this way, but it should be easy to change later
as needed.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/12903#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list