Date: Thu, 14 Mar 2024 21:49:46 +0100 From: Michael Gmelin <grembo@freebsd.org> To: Daniel Engberg <daniel.engberg.lists@pyret.net> Cc: Eugene Grosbein <eugen@grosbein.net>, Florian Smeets <flo@freebsd.org>, ports@freebsd.org Subject: Re: Proposed ports deprecation and removal policy Message-ID: <EF5FD6F9-D6EA-45F6-8845-B0476D401EBB@freebsd.org> In-Reply-To: <7a7501f71442d27f6d8c1c0a16f247c1@mail.infomaniak.com> References: <7a7501f71442d27f6d8c1c0a16f247c1@mail.infomaniak.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 14. Mar 2024, at 21:38, Daniel Engberg <daniel.engberg.lists@pyret.net>= wrote: >=20 > =EF=BB=BFOn 2024-03-12T15:15:49.000+01:00, Eugene Grosbein <eugen@grosbein= .net> wrote: >> 12.03.2024 3:24, Daniel Engberg =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >>=20 >> [skip] >>=20 >>=20 >>> Another possible option would be to add something to the port's mateda= ta that makes pkg aware and easy notiable >>> like using a specific color for portname and related information to sign= al >>> like if it's red it means abandonware and potentially reduced security. >>=20 >> Of course, we need to inform users but not enforce. Tools, not policy. >>=20 > Eugene >=20 > Hi, >=20 > Given that we seem to agree on these points in general why should such por= ts still be kept in the tree? We don't have such tooling available and it wo= nt likely happen anytime soon. Because it's convenient for a committer who u= ses these in a controlled network despite being potentially harmful for othe= rs? >=20 > Just to be clear, I'm after where do we draw the line in general. >=20 > If we look at other distros in general based on availability the decision s= eems to favour overall user security than "convenience". Given that we have s= ecurity policies etc in place I'd say that we in general are leaning towards= user security? So your proposal is to only have ports in the tree that are safe to run on u= nprotected public networks? -m
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EF5FD6F9-D6EA-45F6-8845-B0476D401EBB>