all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: Jesse Gibbons <jgibbons2357@gmail.com>
Cc: 37405@debbugs.gnu.org
Subject: [bug#37405] [PATCH] Services: Check and modify gdm-password in pam-limits
Date: Wed, 2 Oct 2019 01:00:32 +0200	[thread overview]
Message-ID: <20191002010032.1f01e2b0@scratchpost.org> (raw)
In-Reply-To: <461364c376c0c54f0bfff80ed7727d182400671f.camel@gmail.com>

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

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.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-10-01 23:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-14 23:10 [bug#37405] [PATCH] Services: Check and modify gdm-password in pam-limits Jesse Gibbons
2019-09-19  2:46 ` Jesse Gibbons
2019-09-25 15:47   ` Jesse Gibbons
2019-10-01 23:00     ` Danny Milosavljevic [this message]
2019-10-02 14:53       ` Jesse Gibbons

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=20191002010032.1f01e2b0@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=37405@debbugs.gnu.org \
    --cc=jgibbons2357@gmail.com \
    /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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.