On Thu, Apr 16, 2015 at 06:48:53PM +0000, Yawning Angel wrote: > On Thu, 16 Apr 2015 14:03:58 -0400 (EDT) > "Steve Snyder" <swsny...@snydernet.net> wrote: > > The v0.5 binary is substantially larger than the v0.4 binary (7204KB > > vs.5408KB, both built with Go v1.4.2). > > > > Is this expected behavior with the newer version of obfs4proxy? > > Building on linux/amd64 with 1.4.2 I get: > > * 0.0.4 7441792 > * 0.0.5 7424544 > > If I strip either binary I get something in the 5 MiB range, so that > might be where the difference is coming from, though I would strongly > discourage doing so as it is not something that is supported by the > toolchain developers[0], and if a binary that has been stripped breaks, > I'm not going to do anything about it beyond saying "don't do that".
In Tor Browser we build with go build -ldflags '-s' https://gitweb.torproject.org/builders/tor-browser-bundle.git/tree/gitian/descriptors/linux/gitian-pluggable-transports.yml?id=d4e10e98af5237ed21796a4d48c3e09db6994959#n209 Check discussion here: https://trac.torproject.org/projects/tor/ticket/12649 David Fifield _______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev