From d5280a38761a558c32c32e1e277ebd26f63af5c7 Mon Sep 17 00:00:00 2001 From: Ray Strode Date: Fri, 14 Jul 2017 16:05:46 -0400 Subject: daemon: introduce pam extension mechanism This abuses PAM_BINARY_PROMPT for our own nefarious purposes. The way it works is GDM advertises what "extensions" it supports with the environment variable, GDM_SUPPORTED_PAM_EXTENSIONS (a space separated list of reverse dns notation names). PAM services that support this protocol, will read the environment variable, and check for extension strings they support. They then know that sending PAM_BINARY_PROMPT won't blow up, and know what format to use for the binary data. The type field of the structure is the index of the string from the environment variable. This commit is just foundation work. It doesn't actually add any extensions. https://bugzilla.gnome.org/show_bug.cgi?id=788851 --- pam-extensions/gdm-pam-extensions.pc.in | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 pam-extensions/gdm-pam-extensions.pc.in (limited to 'pam-extensions/gdm-pam-extensions.pc.in') diff --git a/pam-extensions/gdm-pam-extensions.pc.in b/pam-extensions/gdm-pam-extensions.pc.in new file mode 100644 index 00000000..5fc64b01 --- /dev/null +++ b/pam-extensions/gdm-pam-extensions.pc.in @@ -0,0 +1,9 @@ +prefix=@prefix@ +exec_prefix=@exec_prefix@ +libdir=@libdir@ +includedir=@includedir@ + +Name: GDM PAM Extensions +Description: Macros for custom protocols over PAM +Version: @VERSION@ +Cflags: -I${includedir}/gdm -- cgit v1.2.1