obfsclient is a C++11 Tor-managed pluggable transport client implementation of the following protocols: obfs2 - The Twobfuscator obfs3 - The Threebfuscator ScrambleSuit - Experimental WWW: https://github.com/yawning/obfsclient -- This port depends on devel/liballium which I submitted as ports/187926. Note that I'm intentionally not using the still-optional LICENSE "framework" in my ports until it's properly maintained, documented and the legal aspects are clear. Please do not add LICENSE* goo to this port without discussing it with me first. Thanks. Redports build logs are available at (the two failures are Redports' issues): https://redports.org/buildarchive/20140325101115-28920/ Fix: Patch attached with submission follows:
Hi, if you are still interested in having this port in FreeBSD, it may (or may not) need to be reworked to support stage, and it may need updating to other newer conventions such as "USES" which is expanding all time. For staging, see http://lists.freebsd.org/pipermail/freebsd-ports-announce/2014-May/000080.html Additionally, you need to provide some sort of quality assurance. In order of preference, we are looking for: 1) "poudriere testport" or "poudriere bulk -t" logs 2) Redports or tinderbox logs Please provide an updated shar file and attach a test log. Alternatively, please indicate if you are no longer interested in having this software in the Ports Collection and that we can close the PR. Thanks!
Created attachment 145462 [details] Updated security/obfsclient port The port builds without warnings on my 11.0-CURRENT system using DEVELOPER=yes. My impression is that Redports doesn't support Uses=libtool yet, but I'll look into this tomorrow.
If you can't do the first two options, doing this: https://www.freebsd.org/doc/en/books/porters-handbook/porting-testing.html Is a (risky for us) third option that I'd accept. Particularly interesting is output of make check-plist and make stage-qa
Committed with modifications.