From nobody Sun Feb 6 06:11:57 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 3CB1419B7872 for ; Sun, 6 Feb 2022 06:12:06 +0000 (UTC) (envelope-from nc@FreeBSD.org) Received: from thunderstorm.neelc.org (thunderstorm.neelc.org [66.42.64.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4JrzSj01NCz3Fkh for ; Sun, 6 Feb 2022 06:12:05 +0000 (UTC) (envelope-from nc@FreeBSD.org) Received: from mail.neelc.org (thunderstorm.neelc.org [IPv6:2001:19f0:8001:174b:5400:3ff:febf:260b]) by thunderstorm.neelc.org (Postfix) with ESMTPSA id 386452FAF1A for ; Sat, 5 Feb 2022 22:11:57 -0800 (PST) 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 Date: Sat, 05 Feb 2022 22:11:57 -0800 From: Neel Chauhan To: ports@freebsd.org Subject: security/sssd: Maintainer inactive? User-Agent: Roundcube Webmail/1.4.13 Message-ID: <4ad930a0fcffffad18a11b6f08b53b5c@FreeBSD.org> X-Sender: nc@FreeBSD.org Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4JrzSj01NCz3Fkh X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=softfail (mx1.freebsd.org: 66.42.64.109 is neither permitted nor denied by domain of nc@FreeBSD.org) smtp.mailfrom=nc@FreeBSD.org X-Spamd-Result: default: False [-2.04 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FREEFALL_USER(0.00)[nc]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[ports@freebsd.org]; TO_DN_NONE(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all:c]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; DMARC_NA(0.00)[FreeBSD.org]; NEURAL_HAM_SHORT(-1.00)[-0.998]; NEURAL_HAM_MEDIUM(-0.94)[-0.940]; MLMMJ_DEST(0.00)[ports]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:20473, ipnet:66.42.64.0/20, country:US]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[]; TO_DOM_EQ_FROM_DOM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N Hi ports@, I was looking at the port security/sssd (mainly to connect FreeBSD to a Windows Server 2022 AD), and noticed the maintainer is inactive. sssd has multiple maintainer timeouts: https://www.freshports.org/security/sssd I don't know if we should reset the maintainership of this port or not. If we do reset, I'm not 100% sure if I want to take on maintainership of the port, but can consider it as a last resort. Disclaimer: I work at Microsoft (which is how I got WS2022), but not on Windows or AD. -Neel (nc@)