Pam-developers November 2013

pam-developers@lists.fedorahosted.org

4 participants
17 discussions

[linux-pam] #4: [PATCH] po/ja.po: Fix some wrong translations and so on
by fedora-badges 26 May '15

26 May '15

#4: [PATCH] po/ja.po: Fix some wrong translations and so on --------------------+------------------------------------------------------- Reporter: fumiyas | Owner: pam-developers(a)lists.fedorahosted.org Type: defect | Status: new Priority: major | Component: library Version: 1.1.x | Keywords: l10n --------------------+------------------------------------------------------- I've updated po/ja.po to fix some wrong translations and so on. Please see and commit the attached patch to master repository if you feel good. Should I contact the original translator (Kiyoto Hashida <khashida(a)redhat.com>) to check and confirm this patch? -- Ticket URL: <https://fedorahosted.org/linux-pam/ticket/4> linux-pam <http://fedorahosted.org/linux-pam> The Linux-PAM (Pluggable Authentication Modules) project

1 9

[linux-pam] #24: [PATCH] pam_env: Expand @{HOME} and @{SHELL}
by fedora-badges 25 Mar '15

25 Mar '15

#24: [PATCH] pam_env: Expand @{HOME} and @{SHELL} --------------------------+------------------------------ Reporter: chrisse | Owner: pam-developers@… Type: enhancement | Status: new Priority: major | Component: modules Version: | Keywords: Blocked By: | Blocking: --------------------------+------------------------------ I came across the problem of trying to modify XDG_DATA_HOME etc. to some other value. pam_env seems to be the ideal point to set those variables, and pam_env.conf supports expansions. However, as already explained in the configuration examples, the ${HOME} environment variable is only set later from the process calling PAM, so there is currently no possibility to actually use this feature. The following patch adds support to expand @{SHELL} and @{HOME}. It does so by looking up the password database entry corresponding to the user and returning the pw_dir and pw_shell fields. The patch works, but it is not complete, since it does not update the documentation. I consider it to be a proof of concept, since I didn't know where exactly to fit in this functionality in the existing code. -- Ticket URL: <https://fedorahosted.org/linux-pam/ticket/24> linux-pam <http://fedorahosted.org/linux-pam> The Linux-PAM (Pluggable Authentication Modules) project

1 4

[linux-pam] #20: compilation warnings
by fedora-badges 24 Mar '15

24 Mar '15

#20: compilation warnings ---------------------+------------------------------ Reporter: mirraz | Owner: pam-developers@… Type: defect | Status: new Priority: minor | Component: library Version: | Keywords: Blocked By: | Blocking: ---------------------+------------------------------ Building pam-1.1.6 I'v got this compilation warnings: {{{ md5.c:145:2: warning: dereferencing type-punned pointer will break strict- aliasing rules [-Wstrict-aliasing] md5.c:146:2: warning: dereferencing type-punned pointer will break strict- aliasing rules [-Wstrict-aliasing] misc_conv.c:213:22: warning: the address of ‘line’ will always evaluate as ‘true’ [-Waddress] misc_conv.c:325:15: warning: the address of ‘binary_prompt’ will always evaluate as ‘true’ [-Waddress] }}} -- Ticket URL: <https://fedorahosted.org/linux-pam/ticket/20> linux-pam <http://fedorahosted.org/linux-pam> The Linux-PAM (Pluggable Authentication Modules) project

1 3

[linux-pam] #9: Allow pam_lastlog to write to utmp as an option
by fedora-badges 24 Mar '15

24 Mar '15

#9: Allow pam_lastlog to write to utmp as an option -------------------------+------------------------------------------------- Reporter: | Owner: pam-developers@… shadowkyogre | Status: new Type: | Component: modules enhancement | Keywords: pam_lastlog utmp update patch Priority: major | prototype Version: 1.1.x | Blocking: Blocked By: | -------------------------+------------------------------------------------- The following patch for pam_lastlog allows it to write to utmp as well as wtmp. Part of the code is from xorg-sessreg to help make a utmp entry. I only tested this on my desktop, which is running Arch Linux, so some modifications may need to be made in order to make it more portable. -- Ticket URL: <https://fedorahosted.org/linux-pam/ticket/9> linux-pam <http://fedorahosted.org/linux-pam> The Linux-PAM (Pluggable Authentication Modules) project

1 4

[linux-pam] #11: sign the released tarballs
by fedora-badges 24 Mar '15

24 Mar '15

#11: sign the released tarballs ---------------------+------------------------------ Reporter: vbatts | Owner: pam-developers@… Type: defect | Status: new Priority: major | Component: library Version: | Keywords: Blocked By: | Blocking: ---------------------+------------------------------ Previously the tarballs that landed on kernel.org were signed by the trusted key 0x517D0F0E, but now the tarballs on https://fedorahosted.org/releases/l/i/linux-pam/ have no signature at all. We not be using Linux-PAM source that does not have a trusted signature. -- Ticket URL: <https://fedorahosted.org/linux-pam/ticket/11> linux-pam <http://fedorahosted.org/linux-pam> The Linux-PAM (Pluggable Authentication Modules) project

3 4

[linux-pam] #21: Fix CPPFLAGS when cross compiling
by fedora-badges 10 Dec '14

10 Dec '14

#21: Fix CPPFLAGS when cross compiling ---------------------+------------------------------ Reporter: zlin | Owner: pam-developers@… Type: defect | Status: new Priority: major | Component: library Version: 1.1.x | Keywords: Blocked By: | Blocking: ---------------------+------------------------------ When cross compiling for arm for instance the build will fail if CPPFLAGS does not get respected. -- Ticket URL: <https://fedorahosted.org/linux-pam/ticket/21> linux-pam <http://fedorahosted.org/linux-pam> The Linux-PAM (Pluggable Authentication Modules) project

1 1

[PATCH 2/2] Modernize AM_INIT_AUTOMAKE invocation
by Dmitry V. Levin 28 Jan '14

28 Jan '14

Before this change, automake complained that two- and three-arguments forms of AM_INIT_AUTOMAKE are deprecated. * configure.in: Pass PACKAGE and VERSION arguments to AC_INIT instead of AM_INIT_AUTOMAKE. --- configure.in | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/configure.in b/configure.in index f16020b..a161e20 100644 --- a/configure.in +++ b/configure.in @@ -1,8 +1,8 @@ dnl Process this file with autoconf to produce a configure script. -AC_INIT +AC_INIT([Linux-PAM], [1.1.8]) AC_CONFIG_SRCDIR([conf/pam_conv1/pam_conv_y.y]) AC_CONFIG_AUX_DIR([build-aux]) -AM_INIT_AUTOMAKE("Linux-PAM", 1.1.8) +AM_INIT_AUTOMAKE AC_PREREQ([2.61]) AC_CONFIG_HEADERS([config.h]) AC_CONFIG_MACRO_DIR([m4]) -- ldv

2 2

[linux-pam] #5: multiple pam_namespace unmount problems
by fedora-badges 23 Jan '14

23 Jan '14

#5: multiple pam_namespace unmount problems -----------------------------+------------------------------ Reporter: andersblomdell | Owner: pam-developers@… Type: defect | Status: new Priority: major | Component: library Version: 1.1.x | Keywords: Blocked By: | Blocking: -----------------------------+------------------------------ This is essentially a short version of the bug in: http://bugzilla.redhat.com/show_bug.cgi?id=755216 Essentially pam_namespace (1.1.5) suffers the following problems: 1. The (bind) mounts done in the new namespace is visible in the original namespace (Error "too many levels of symbolic links"). 2. At pam_namespace exit, the original mounting is restored for any remaining child processes (daemons), which is a security problem. Patch is attached -- Ticket URL: <https://fedorahosted.org/linux-pam/ticket/5> linux-pam <http://fedorahosted.org/linux-pam> The Linux-PAM (Pluggable Authentication Modules) project

1 2

[linux-pam] #22: pam_mkhomedir uses user alias username instead of canonical name when creating home directories
by fedora-badges 21 Jan '14

21 Jan '14

#22: pam_mkhomedir uses user alias username instead of canonical name when creating home directories -------------------------+------------------------------------------------- Reporter: | Owner: pam-developers@… musicalvegan0 | Status: new Type: defect | Component: modules Priority: major | Keywords: sssd, ipa, active directory, Version: 1.1.x | mkhomedir Blocked By: | Blocking: -------------------------+------------------------------------------------- When logging in with an "alias" for the first time, mkhomedir will take the alias of the user instead of looking up the canonical name associated with the alias. This can lead to the creation of the wrong home directory and ends up putting the user somewhere other than their home directory. Please see this listserv archive for additional context: https://lists.fedorahosted.org/pipermail/sssd- users/2013-October/001056.html Steps to reproduce: 1. Create a user account with an alias on a directory server. 2. Configure PAM to authenticate against the directory server. 3. Configure PAM with pam_mkhomedir.so so home directories are created for first time logins. 4. Login for the first time with the user's alias. What is expected to happen: The proper home directory is created and the user is chdir-ed into it. What actually happens: This can vary. In my case, the user's home directory path is not retrieved from the directory server and a fallback home directory is erroneously created. The user is not started in the proper home directory. -- Ticket URL: <https://fedorahosted.org/linux-pam/ticket/22> linux-pam <http://fedorahosted.org/linux-pam> The Linux-PAM (Pluggable Authentication Modules) project

1 7

[linux-pam] #19: logger message uses uninitialized char buffer in group_match() of pam_access.c
by fedora-badges 19 Jan '14

19 Jan '14

#19: logger message uses uninitialized char buffer in group_match() of pam_access.c -----------------------+------------------------------ Reporter: nickfelt | Owner: pam-developers@… Type: defect | Status: new Priority: minor | Component: modules Version: 1.1.x | Keywords: Blocked By: | Blocking: -----------------------+------------------------------ I was debugging my configuration of the pam_access module and noticed some strange behavior in the debug-level logging messages, which I traced to the `group_match()` function: [https://git.fedorahosted.org/cgit/linux- pam.git/tree/modules/pam_access/pam_access.c#n566] On line 576 it writes a log message using the `grptok` char buffer, which has just been declared and not initialized. Presumably the logging call should either use `tok` instead to print the group name in parentheses, or the logging call should be moved below the `strncpy()` call, at which point `grptok` is valid, to print the group name without parentheses. I would've attached a patch but I wasn't sure which solution was preferable. At least on my machine, the current code prints an empty string on the first call to `group_match` and then on each successive call it prints the value of grptok corresponding to the previous call to `group_match` that is still in the buffer. I've attached my test-case `/etc/security/access.conf` and the logging output I saw. -- Ticket URL: <https://fedorahosted.org/linux-pam/ticket/19> linux-pam <http://fedorahosted.org/linux-pam> The Linux-PAM (Pluggable Authentication Modules) project

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Pam-developers November 2013