From nobody Mon Jan 24 12:10:11 2022 X-Original-To: ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 866FB1985645 for ; Mon, 24 Jan 2022 12:10:21 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (fbsd.rdg.namesco.net [213.246.108.13]) by mx1.freebsd.org (Postfix) with ESMTP id 4Jj82351lHz3JFT for ; Mon, 24 Jan 2022 12:10:19 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from [192.168.1.111] (vhoffman.plus.com [81.174.148.213]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by unsane.co.uk (Postfix) with ESMTPSA id 472F33021F for ; Mon, 24 Jan 2022 12:10:12 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=unsane.co.uk; s=251017; t=1643026212; bh=o06P8guSvA08+9vGQmQjF5qpPMM/Pbpis4YGo3cmZrI=; h=Date:To:References:From:Subject:In-Reply-To; b=gmElYjK1rlXHtpclvyq/p0/SOBkc82NZN7GRLjupasx7G6tLVzmyh1U08dK0iZJr0 OnALd/P6qEucNZ4OfP0GktekyAX+27Q41WTBf0eSoIhXgjU71OU9Oy/f41MNqTi9Vy 90x40nxOgX+zdRoKkWZT1PKbRxSKHZmny5oZvprg= Message-ID: <77575554-ac59-746c-c506-fd33fb4bc206@unsane.co.uk> Date: Mon, 24 Jan 2022 12:10:11 +0000 List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Content-Language: en-US To: ports@freebsd.org References: <20220120142519.a5juoe75oppmnyby@aniel.nours.eu> <20220124085941.lklzatk6u7dnqbuj@aniel.nours.eu> From: Vincent Hoffman-Kazlauskas Subject: Re: [HEADSUP] Deprecation of the ftp support in pkg In-Reply-To: <20220124085941.lklzatk6u7dnqbuj@aniel.nours.eu> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Jj82351lHz3JFT X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unsane.co.uk header.s=251017 header.b=gmElYjK1; dmarc=pass (policy=none) header.from=unsane.co.uk; spf=pass (mx1.freebsd.org: domain of vince@unsane.co.uk designates 213.246.108.13 as permitted sender) smtp.mailfrom=vince@unsane.co.uk X-Spamd-Result: default: False [-3.90 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[unsane.co.uk:s=251017]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+a]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[ports@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; DKIM_TRACE(0.00)[unsane.co.uk:+]; DMARC_POLICY_ALLOW(-0.50)[unsane.co.uk,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MLMMJ_DEST(0.00)[ports]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:8622, ipnet:213.246.64.0/18, country:GB]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On 24/01/2022 08:59, Baptiste Daroussin wrote: > On Mon, Jan 24, 2022 at 12:12:20AM -0800, Chris wrote: >> On 2022-01-23 10:19, Patrick M. Hausen wrote: >>> Hi all, >>> >> > > based on the discussion I am adding right now, a new protocol: tcp:// which uses > the protocol we made on top of ssh way simple than ftp and capsicumized on the > server side), but without the requirement for a ssh connection. > > This will enable people with performance concern but still willing to have data > encrypted to use spiped or socat for example as a transport. > > And for other a simple inetd will work. > > on inetd.conf > > pkg stream tcp nowait nobody /usr/local/sbin/pkg -- -o SSH_RESTRICT_DIR=/mypackages ssh > > > and define in /etc/services "pkg" to the port you want pkg to be serving its > files to. > > for the repo on the pkg side: > > tcp://url:port/mypackages > > What do you think? > Not having a preference re: ftp I think this tcp:// option looks very useful. As an aside has anyone written up how to setup a repo over ssh? I've had a quick google with no luck. I'm sure its not too tricky and an hour or so I could work it out but if anyone has already done it that would be great. Thanks, Vince > For me as a maintainer it is very few lines of code to add, the protocol > itself being already written, way easier to suppoer and it provides an interesting feature > by the ability to serve via spiped or inetd. > > Best regards, > Bapt >