Re: [tor-dev] Reproducibility of Pluggable Transports python.msi

David Fifield transcribed 1.4K bytes: > On Wed, Sep 09, 2015 at 03:33:24PM -0400, Brandon Wiley wrote: > > I am in favor of standardizing on the Go codebase for pluggable transports > > that > > ship with Tor. This is something we talked about at the last developer > > meeting. > > The reason I

Re: [tor-dev] Reproducibility of Pluggable Transports python.msi

On Thu, Sep 10, 2015 at 12:55 AM, Yawning Angel wrote: > > FWIW, I don't particularly think that there must be One True PT > language[0], I just recommend Go over the other alternatives due to it > being both memory safe and easy to build on mobile. If someone writes a >

Re: [tor-dev] Reproducibility of Pluggable Transports python.msi

On Thu, 10 Sep 2015 10:20:59 -0400 Brandon Wiley wrote: > I'm not advocating that the various PT implementations be abandoned, > just that we have a common implementation across products when > possible. If I recall correctly, there was a time when TBB, Tails, > and Orbot were

Re: [tor-dev] Reproducibility of Pluggable Transports python.msi

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/09/2015 07:33 PM, Brandon Wiley wrote: > I also don't know how well reproducible builds work with Go, so if > someone knows that would be interesting information. Take a look here:

Re: [tor-dev] Reproducibility of Pluggable Transports python.msi

On Wed, 9 Sep 2015 17:20:11 -0400 Brandon Wiley wrote: > Thanks David, great info! Last time I checked, I think the C > implementation was also still shipping with something, I think Orbot > for Android. Perhaps this is also for either flash proxy or FTE > support, since Python

Re: [tor-dev] Reproducibility of Pluggable Transports python.msi

Another option here, besides getting python to build in gitian is to phase out support for python-based pluggable transports. It's something to consider at least. Which transports are still only available in python? On Sun, Sep 6, 2015 at 7:26 PM, Jeremy Rand wrote: >

Re: [tor-dev] Reproducibility of Pluggable Transports python.msi

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/09/2015 06:43 PM, Brandon Wiley wrote: > Another option here, besides getting python to build in gitian is > to phase out support for python-based pluggable transports. It's > something to consider at least. Which transports are still only >

Re: [tor-dev] Reproducibility of Pluggable Transports python.msi

On Wed, Sep 09, 2015 at 03:33:24PM -0400, Brandon Wiley wrote: > I am in favor of standardizing on the Go codebase for pluggable transports > that > ship with Tor. This is something we talked about at the last developer > meeting. > The reason I favor this is not for reproducible build reasons,

Re: [tor-dev] Reproducibility of Pluggable Transports python.msi

I am in favor of standardizing on the Go codebase for pluggable transports that ship with Tor. This is something we talked about at the last developer meeting. The reason I favor this is not for reproducible build reasons, but because maintaining four implementations (C, Python, C++, and Go) is

Re: [tor-dev] Reproducibility of Pluggable Transports python.msi

Thanks David, great info! Last time I checked, I think the C implementation was also still shipping with something, I think Orbot for Android. Perhaps this is also for either flash proxy or FTE support, since Python is not the best option on Android. >From the graphs it looks like FTE is still in

Re: [tor-dev] Reproducibility of Pluggable Transports python.msi

On Sun, Sep 06, 2015 at 11:26:16PM +, Jeremy Rand wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > I was looking at the Gitian descriptor for the pluggable transports at > https://gitweb.torproject.org/builders/tor-browser-bundle.git/tree/gitia >

[tor-dev] Reproducibility of Pluggable Transports python.msi

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I was looking at the Gitian descriptor for the pluggable transports at https://gitweb.torproject.org/builders/tor-browser-bundle.git/tree/gitia n/descriptors/windows/gitian-pluggable-transports.yml , and I noticed that it has an input file called