From owner-freebsd-ports@FreeBSD.ORG Sat Nov 9 14:22:52 2013 Return-Path: Delivered-To: ports@FreeBSD.org Received: by hub.freebsd.org (Postfix, from userid 1033) id C5223C2D; Sat, 9 Nov 2013 14:22:52 +0000 (UTC) Date: Sat, 9 Nov 2013 14:22:52 +0000 From: Alexey Dokuchaev To: "Julian H. Stacey" Subject: Re: Anyone looked at making a port for https://www.eff.org/https-everywhere ? Message-ID: <20131109142252.GA97651@FreeBSD.org> References: <201311071334.rA7DY0UY015417@fire.js.berklix.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201311071334.rA7DY0UY015417@fire.js.berklix.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: ports@FreeBSD.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Nov 2013 14:22:52 -0000 On Thu, Nov 07, 2013 at 02:34:00PM +0100, Julian H. Stacey wrote: > Has anyone looked at making a ports wrapper for > https://www.eff.org/https-everywhere ? > > Sources: https://www.eff.org/https-everywhere/development > > PS on current/ports, grep https-everywhere shows nothing, > grep www.eff.org shows just security/switzerland/, port creator > Alexey Dokuchaev added to CC. Oh, that's a blast from the past. :) Frankly I already forgot why I decided to port it, probably because I needed it back in those days. I'm afraid I cannot say anything about https-everywhere as a whole. ./danfe