Date: Mon, 10 Oct 2016 16:15:21 +1100 From: Kubilay Kocak <koobs@FreeBSD.org> To: John Kozubik <john@kozubik.com> Cc: freebsd-hackers@freebsd.org, "freebsd-jobs@freebsd.org" <freebsd-jobs@freebsd.org> Subject: Re: Who wants to get paid to maintain sshuttle for FreeBSD ? Message-ID: <83e12460-088d-efbb-0725-ea0a465e7da7@FreeBSD.org> In-Reply-To: <alpine.BSF.2.00.1609290847320.22132@kozubik.com> References: <alpine.BSF.2.00.1609290847320.22132@kozubik.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30/09/2016 1:54 AM, John Kozubik wrote: > > > (yep, cross-posting to jobs and hackers ...) > > > Hello, > > We (myself, rsync.net, 0x.co) are very interested in using sshuttle > on FreeBSD: > > https://github.com/sshuttle > > However the tool has never quite worked properly on FreeBSD[1] and > there appears to be no FreeBSD specific development that gets > contributed to it. > > We would like to pay someone - first to do some heavy lifting and > bring the project up to speed for FreeBSD, but then on a continued > basis to ensure it *keeps* working over time. Presumably this > involves creating a FreeBSD port as well as fixing the big issues. > > This is a job for someone who understands well the FreeBSD > networking stack, ipfw and NAT rules, and who has a small but > consistent amount of time to devote to this over the next few years. > > You would be paid as an independent contractor by rsync.net, Inc. > > Please email me and let me now if this interests you. > > Thanks, > > John Kozubik rsync.net / 0x.co > > > [1] DNS and UDP "leak" from the tunnel, among other things... John, I've gone ahead and just created/committed a port for sshuttle, including hooking up the test suite to the ports make test command to make QA and reporting an initial set of issues upstream much easier: https://svnweb.freebsd.org/changeset/ports/423637 I note several test (F)ailures to the the use of raising exceptions (rather than failing assert()'s), some (most?) of which at initial glance appear to be related to tests that utilise or test tproxy() functionality. Tests failing in that manner should instead be skipped on FreeBSD (and any other environment without tproxy support). A second set of failing tests appears to be related to IPv6 (only supported by sshuttle for tproxy method, as per docs) which again I believe should be skipped on environments without tproxy support. Perhaps this is a good first step to progress upstream, but I'm also happy to provide upstream with FreeBSD buildbots to assist them if they use it (I already do for other OSS projects). Feel free to hit me up off list or on IRC (#freebsd @ freenode) -- Regards, Kubilay
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?83e12460-088d-efbb-0725-ea0a465e7da7>