From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 45860158020 for ; Sun, 11 Dec 2022 15:38:33 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B329DE088C; Sun, 11 Dec 2022 15:38:29 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (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) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 51B6FE086D for ; Sun, 11 Dec 2022 15:38:29 +0000 (UTC) Message-ID: Date: Sun, 11 Dec 2022 16:38:11 +0100 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.1 Subject: Re: [gentoo-dev] pam: thoughts on modernizing pam_limits configuration that Gentoo ships with Content-Language: en-US To: gentoo-dev@lists.gentoo.org References: <8e75c01a-e798-d822-312d-cb21b6d70d45@gentoo.org> From: Piotr Karbowski In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 930d1111-bfd6-4921-a8a5-f64e4f6246bb X-Archives-Hash: a285e228ba5b49050f107a4561db7c86 Hi, On 11/12/2022 13.46, Sam James wrote: > You should still file a bug for two reasons: > 1. Paper trail > 2. sys-auth/pambase has another maintainer who*is* active :) > > As for the question in your post, I'll have a think. Thanks! I am not against creating a bug, I do see it however as inefficient in this very case. I do know however if I were to create bug and assign it to current single pam maintainer, it would hardly get noticed by other people, greatly reducing the feedback. Changing defaults will affect vast majority of Gentoo users, so gentoo-dev ml was the place I choosen. I didn't realized that you are maintainer of pambase, though the /etc/security/limits.conf belongs to sys-libs/pam that has only zlogene. I did mail zlogene regarding another package recently and got no response, thus pam itself seems maintainer-needed to me, and because of it a candidate for me to join as another maintainer and do the changes. I do not think it would make much sense for me to then create bug for myself to make this change of defaults, paper trail would be the commit subject and message itself, or perhaps I did not understood of what you meant here by paper trail, would appreciate clarification. It would be great if you were interested in joining pam itself, and I am interested to also joining pambase, since those are so co-dependent it does not make sense to have split maintainers there. -- Piotr.