public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] pam: thoughts on modernizing pam_limits configuration that Gentoo ships with
Date: Sun, 11 Dec 2022 12:46:03 +0000	[thread overview]
Message-ID: <FC4618C0-28F2-4C41-A730-DA07AA9963F9@gentoo.org> (raw)
In-Reply-To: <8e75c01a-e798-d822-312d-cb21b6d70d45@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 750 bytes --]



> On 11 Dec 2022, at 08:28, Piotr Karbowski <slashbeast@gentoo.org> wrote:
> 
> Hi,
> 
> I'd like to touch base on the topic of pam_limits and the defaults that we ended up with in Gentoo.
> 
> [...]
> 
> Any thoughts?
> 
> Unless there's strong opposition to not bump those 1024/4096 current defaults, I'd like to bump those limits. Normally I'd create a bug and assign it to maintainer, however our sys-libs/pam maintainer has not been seen in last half a year, so I'd end up joining as co-maintainer there in the result.
> 

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!

Best,
sam


[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]

  reply	other threads:[~2022-12-11 12:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-11  8:28 [gentoo-dev] pam: thoughts on modernizing pam_limits configuration that Gentoo ships with Piotr Karbowski
2022-12-11 12:46 ` Sam James [this message]
2022-12-11 15:38   ` Piotr Karbowski
2022-12-12  5:52 ` Robin H. Johnson
2022-12-12 21:55   ` Piotr Karbowski
2022-12-12 22:06     ` Sam James
2022-12-12 22:26       ` Piotr Karbowski
2022-12-12 22:53         ` Sam James
2022-12-13  3:24         ` John Helmert III
2022-12-13  5:18         ` Joonas Niilola

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=FC4618C0-28F2-4C41-A730-DA07AA9963F9@gentoo.org \
    --to=sam@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox