From debbugs-submit-bounces@debbugs.gnu.org Tue Oct 01 19:00:38 2019 Received: (at 37405) by debbugs.gnu.org; 1 Oct 2019 23:00:38 +0000 Received: from localhost ([127.0.0.1]:35189 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iFR8I-00018w-DB for submit@debbugs.gnu.org; Tue, 01 Oct 2019 19:00:38 -0400 Received: from dd26836.kasserver.com ([85.13.145.193]:59042) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iFR8G-00018n-JN for 37405@debbugs.gnu.org; Tue, 01 Oct 2019 19:00:37 -0400 Received: from localhost (77.117.238.108.wireless.dyn.drei.com [77.117.238.108]) by dd26836.kasserver.com (Postfix) with ESMTPSA id 8972C3363BEE; Wed, 2 Oct 2019 01:00:34 +0200 (CEST) Date: Wed, 2 Oct 2019 01:00:32 +0200 From: Danny Milosavljevic To: Jesse Gibbons Subject: Re: [bug#37405] [PATCH] Services: Check and modify gdm-password in pam-limits Message-ID: <20191002010032.1f01e2b0@scratchpost.org> In-Reply-To: <461364c376c0c54f0bfff80ed7727d182400671f.camel@gmail.com> References: <14cd3e26c2dae4de79a2bc87fb8614c8f737e629.camel@gmail.com> <461364c376c0c54f0bfff80ed7727d182400671f.camel@gmail.com> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-unknown-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/bNbg7G.MCo3vu8RSWpOxoPy"; protocol="application/pgp-signature" X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 37405 Cc: 37405@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) --Sig_/bNbg7G.MCo3vu8RSWpOxoPy Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi, thanks for the patch. I'm not thrilled about that approach (arguably Guix already does it wrong anyway). But since the manual of pam_limits does describe that one should use it like that, I have applied it as a stop-gap fix to guix master as commit 0bf7d34d77ffca40be9e04586195054e9f2c7a13. Long term, we should really make pam entries first class and show up in the operating-system record--that's what they are FOR: to let the administrator (and thus the organization) choose how they want to do user authorization/session handling etc. Why do we decide for them? Bug report kept open for obvious reasons. --Sig_/bNbg7G.MCo3vu8RSWpOxoPy Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAl2T2pAACgkQ5xo1VCww uqWlngf/UKMtNSKEbEGkkUEDqY0mx4JorRQJ9TQr3rc1EJzmudieoz8JScnRYF4M Nm7JIbroSuxZNbtx9TIJD+gbJdySrc57u6xTaY7TVlGthtgamYuLh9HSKEb/z0WS sGV5C/5qqVdQqyNMOS/D+DSb+Yk4BA98F9FAzB79AYEUR6xNNaNPPTboO5exG7/B ZWnhmfQt890pNPD5Ik0RaAG1zCr+9ZbD+qyDqKxIF79JQzW/gGARagqgAeGFCTS1 75kqqVaFBb2ISjgqyajsl60iKm/+sWMq14KeSczYt/GrbvI3luYw31SKJCcU9Y3B YkfVjpUljE1CG1AtJIg4r78LWeqbHQ== =DZSK -----END PGP SIGNATURE----- --Sig_/bNbg7G.MCo3vu8RSWpOxoPy--