From: Maxime Devos <maximedevos@telenet.be>
To: Maya <maya.omase@protonmail.com>, 56797@debbugs.gnu.org
Subject: [bug#56797] [PATCH] gnu: services: fprintd: Add PAM configuration.
Date: Wed, 27 Jul 2022 18:12:17 +0200 [thread overview]
Message-ID: <067bff4c-3ada-0597-2632-9482066df2f2@telenet.be> (raw)
In-Reply-To: <4AtymQ5ic7YPCQjgRG3Dj73aZuO_Rx7GX8YSKBPeoVoOG_Z8LjXXbqvvfaq-ap0fgLADcsE8zibqDwkO7kazYXa0eMA3EeEaiU_6wGQ0yI8=@protonmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 2044 bytes --]
On 27-07-2022 17:57, Maya via Guix-patches via wrote:
> Added a feature to fprintd-service-type to allow unlocking PAM modules (ie. gdm login, gnome polkit etc.) by fingerprint.
>
> ---
Documentation is missing (in the manual), so as-is, this new feature is
hard to find.
Also, the manual required giving every top-level procedure a docstring
IIRC,
> gnu/services/authentication.scm | 49 +++++++++++++++++++++++++++++++--
> 1 file changed, 46 insertions(+), 3 deletions(-)
>
> diff --git a/gnu/services/authentication.scm b/gnu/services/authentication.scm
> index f7becdfafb..5737c15f4c 100644
> --- a/gnu/services/authentication.scm
> +++ b/gnu/services/authentication.scm
> @@ -44,9 +44,50 @@ (define-module (gnu services authentication)
> nslcd-configuration?
> nslcd-service-type))
>
> -(define-configuration fprintd-configuration
> +(define-configuration/no-serialization fprintd-configuration
> (fprintd (file-like fprintd)
> - "The fprintd package"))
> + "The fprintd package")
> + (unlock-gdm?
> + (boolean #t)
> + "Generate PAM configuration that unlocks gdm with fprintd.")
> + (unlock-other
> + (list '("polkit-1" "sddm")) ;; polkit-1 is the name of a PAM module for GNOME polkit
> + "List of other PAM modules that can be unlocked with fprintd.
> +
> +This depends on your desktop configuration. If you for example want GNOME prompts to be unlocked by fingerprint, you add @code{polkit-1} to this list. (This is enabled by default.)
> +"))
This documentation is unclear -- does this field need to be set to the
_name_ of the module, or to the _file name_ of the _shared library_ (as
a file-like, not a direct file name, because of staging), or ...? Also,
the 'list' check can be more precise, IIRC there was some method for not
just using list? but doing things like list-of-strings?.
Anyway, I don't really know PAM, but I've written some comments on the
patch, hopefullt they are useful.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-07-27 16:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 15:57 [bug#56797] [PATCH] gnu: services: fprintd: Add PAM configuration Maya via Guix-patches via
2022-07-27 16:04 ` Maxime Devos
2022-07-27 16:06 ` Maxime Devos
2022-07-27 16:12 ` Maxime Devos [this message]
2022-07-27 20:26 ` Maya via Guix-patches via
2022-07-27 21:56 ` Maxime Devos
2022-08-09 15:00 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=067bff4c-3ada-0597-2632-9482066df2f2@telenet.be \
--to=maximedevos@telenet.be \
--cc=56797@debbugs.gnu.org \
--cc=maya.omase@protonmail.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).