From nobody Wed Mar 20 01:03:27 2024 X-Original-To: freebsd-current@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 4Tzr1y3nCsz5FxJW for ; Wed, 20 Mar 2024 01:03:34 +0000 (UTC) (envelope-from agh@riseup.net) Received: from mx0.riseup.net (mx0.riseup.net [198.252.153.6]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx0.riseup.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Tzr1y0qFkz4WZ4 for ; Wed, 20 Mar 2024 01:03:34 +0000 (UTC) (envelope-from agh@riseup.net) Authentication-Results: mx1.freebsd.org; none Received: from fews01-sea.riseup.net (fews01-sea-pn.riseup.net [10.0.1.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx0.riseup.net (Postfix) with ESMTPS id 4Tzr1q6ygRz9sM5; Wed, 20 Mar 2024 01:03:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1710896608; bh=wK5XCmiI2jrdZBNpXwuguZy8EpUyCUU20EgVCCOtstE=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=bu1GnOeF2UJz1olNge3nNLu6edp2rsgCp3TPynnlqlQJllGRaiRFjiB93gLRNQV5F pMmNMuLYm+ugItgNV0yfR6SrZnRL21Vw6lvpYGDyXzWFSDuUEuYtf4ijj8E1yhLGlX 1L11mNESr+svwN8MPqeesIPnYsgxZGp+DLa8aUGw= X-Riseup-User-ID: 70FC29C05C2F6E305D5F103D9E0D8B78FB8D90086D39A20851DBA9D954839F85 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4Tzr1q5pCzzJpZq; Wed, 20 Mar 2024 01:03:27 +0000 (UTC) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Date: Wed, 20 Mar 2024 01:03:27 +0000 From: Alastair Hogge To: Emmanuel Vadot Cc: Freebsd Current Subject: Re: sysutils/pam_xdg: Cancelled on -CURRENT In-Reply-To: <20240319090230.3a1e7409578f8f4a373a341e@bidouilliste.com> References: <4e4a5f033f4169dd07f4afdd7b5f6976@riseup.net> <20240319082306.f4ffef050d8439be07b10962@bidouilliste.com> <20240319090230.3a1e7409578f8f4a373a341e@bidouilliste.com> Message-ID: <544b57564b9c5a2749765cf2007c7153@riseup.net> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US] X-Rspamd-Queue-Id: 4Tzr1y0qFkz4WZ4 On 2024-03-19 16:02, Emmanuel Vadot wrote: > On Tue, 19 Mar 2024 07:55:15 +0000 > Alastair Hogge wrote: > >> On 2024-03-19 15:23, Emmanuel Vadot wrote: >> > Hi, >> >> Hey Emmanuel, >> >> > On Tue, 19 Mar 2024 06:54:27 +0000 >> > Alastair Hogge wrote: >> > >> >> Hello, >> >> >> >> Recently a similar module (PAM) mentioned in the subject was committed >> >> to base[1]. The module in base masks the currently installed Port, the >> >> man page can be accessed with man -M /usr/local/share/man 8 pam_xdg, >> >> however, I can now no longer build the Port. I noticed that the base >> >> module has no WITHOUT_ option, tho, that might be extreme for one >> >> module, but then again, the base module masks a more feature full >> >> module. What is the practice to enable use of the Port again? At the >> >> moment I am updating my host, and testing the following: >> >> >> >> diff --git a/lib/libpam/modules/modules.inc >> >> b/lib/libpam/modules/modules.inc >> >> index f3ab65333f4f..ddbb326f0312 100644 >> >> --- a/lib/libpam/modules/modules.inc >> >> +++ b/lib/libpam/modules/modules.inc >> >> @@ -30,4 +30,3 @@ MODULES += pam_ssh >> >> .endif >> >> MODULES += pam_tacplus >> >> MODULES += pam_unix >> >> -MODULES += pam_xdg >> >> \ No newline at end of file >> >> >> >> 1: >> >> https://cgit.freebsd.org/src/commit/?id=6e69612d5df1c1d5bd86990ea4d9a170c030b292 >> >> >> >> Thanks. >> >> >> > >> > I don't see why you can't build the ports. >> >> From sysutils/pam_xdg[2]: >> >> if exists(/usr/lib/pam_xdg.so) >> IGNORE= module name conflict with a different implementation in >> base system >> endif > > Ah yes, I've missed this :) > >> > Using would be a problem but why do you want to use it now that we >> > have one in base ? >> > Do you have any problems with the one in base ? >> >> I would like to continue using sysutils/pam_xdg because it handles all >> ${XDG_*_HOME}, and local name spaces. > > XDG_*_HOME variables aren't needed, all applications must have a > fallback to the base directories in the spec and sysutils/pam_xdg > doesn't offer to use other directories so that's why I didn't implement > those in the base one. > What do you mean by "local name spaces" ? I meant all the other ${XDG_FU} excluding ${XDG_*_HOME}. Anyways, turns out incredibly mistaken. I deployed another corporate craptop from the dumpster today, and the User's homedir was not populated with XDG dirs. I was sure I was using sysutils/pam_xdg for that, but will now have to find my older scripts that predate using sysutils/pam_xdg, to achieve that. Sorry for the noise. Thanks, Alastair