[linux-pam] #4: [PATCH] po/ja.po: Fix some wrong translations and so on
by fedora-badges
#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
8 years, 12 months
[linux-pam] #29: pam_env documentation update
by fedora-badges
#29: pam_env documentation update
--------------------------+------------------------------
Reporter: kohtala | Owner: pam-developers@…
Type: enhancement | Status: new
Priority: major | Component: documentation
Version: 1.1.x | Keywords: pam_env
Blocked By: | Blocking:
--------------------------+------------------------------
I found pam_env and pam_env.conf documents very confusing and incomplete.
Once I figured out how it works, I wrote update.
--
Ticket URL: <https://fedorahosted.org/linux-pam/ticket/29>
linux-pam <http://fedorahosted.org/linux-pam>
The Linux-PAM (Pluggable Authentication Modules) project
9 years, 1 month
[linux-pam] #24: [PATCH] pam_env: Expand @{HOME} and @{SHELL}
by fedora-badges
#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
9 years, 1 month
[linux-pam] #20: compilation warnings
by fedora-badges
#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
9 years, 1 month
[linux-pam] #9: Allow pam_lastlog to write to utmp as an option
by fedora-badges
#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
9 years, 1 month
[linux-pam] #32: pam_timestamp: default TIMESTAMPDIR no longer matches sudo time stamp directory
by fedora-badges
#32: pam_timestamp: default TIMESTAMPDIR no longer matches sudo time stamp
directory
---------------------+------------------------------
Reporter: thoger | Owner: pam-developers@…
Type: defect | Status: new
Priority: minor | Component: modules
Version: | Keywords:
Blocked By: | Blocking:
---------------------+------------------------------
pam_timestamp defaults to using `/var/run/sudo` as its default time stamp
directory. This seems to be for compatibility with sudo. However, that
directory is no longer used by sudo as of version 1.7.4:
http://www.sudo.ws/repos/sudo/rev/8c9440423d98
Starting with sudo 1.7.4, the time stamp files have moved from
/var/run/sudo to either /var/db/sudo, /var/lib/sudo or /var/adm/sudo.
The directories are checked for existence in that order. This
prevents users from receiving the sudo lecture every time the
system reboots. Time stamp files older than the boot time are
ignored on systems where it is possible to determine this.
In Fedora, sudo now uses `/var/db/sudo` directory:
http://pkgs.fedoraproject.org/cgit/sudo.git/commit/?id=e273750
On a quick look, it seems sudo and pam_timestamp now use different time
stamp file content and mode. It seems pam_timestamp assumes sudo times
tamp files are empty, but current sudo versions no longer create empty
files:
https://git.fedorahosted.org/cgit/linux-
pam.git/tree/modules/pam_timestamp/pam_timestamp.c?id=9dcead8#n451
pam_timestamp writes full time stamp file path to the time stamp file,
which does not seem to be done by sudo. I haven't investigated what data
is written by sudo. Also ownership of sudo time stamp file is root:user,
and pam_timestamp expects root:root.
These incompatibility exists with sudo 1.7.2, which still uses
`/var/run/sudo`. It seems this requires more changes and not only change
of `TIMESTAMPDIR` to `/var/db/sudo`.
--
Ticket URL: <https://fedorahosted.org/linux-pam/ticket/32>
linux-pam <http://fedorahosted.org/linux-pam>
The Linux-PAM (Pluggable Authentication Modules) project
9 years, 1 month
[linux-pam] #35: 'logic list' format unexplained in group.conf manpage
by fedora-badges
#35: 'logic list' format unexplained in group.conf manpage
--------------------------+-----------------------------------
Reporter: robinmiller | Owner: pam-developers@…
Type: defect | Status: new
Priority: minor | Component: documentation
Version: | Keywords: group.conf logic list
Blocked By: | Blocking:
--------------------------+-----------------------------------
The group.conf manpage refers to a 'logic list' several times as the way
to specify multiple ttys, users, etc, but does not give a clear example or
describe the syntax required.
After some fruitless searching and then trial and error, I discovered that
the format is:
{{{
item1 | item2 | item3
}}}
I think it would be a big help to users to make this clear in the man
page, either by describing the syntax or by giving a clear example in the
examples section (there is a convoluted example using &, but I don't think
this is obvious at first). For example, the example:
{{{
Running 'xsh' on tty* (any ttyXXX device), the user 'sword' is given
access to games (through membership of the floppy group) after work hours.
xsh; tty* ;sword;!Wk0900-1800;games, sound
}}}
Could be made into:
{{{
Running 'xsh' on tty* (any ttyXXX device), the users 'sword' and 'pike'
are given access to games (through membership of the floppy group) after
work hours.
xsh; tty* ; sword | pike ;!Wk0900-1800;games, sound
}}}
That small change alone would have saved me an hour. Perhaps the term
'logic list' is a well known format to some, but I don't think to many.
--
Ticket URL: <https://fedorahosted.org/linux-pam/ticket/35>
linux-pam <http://fedorahosted.org/linux-pam>
The Linux-PAM (Pluggable Authentication Modules) project
9 years, 1 month
[linux-pam] #33: pam_timestamp: timestampdir option not documented properly
by fedora-badges
#33: pam_timestamp: timestampdir option not documented properly
---------------------+------------------------------
Reporter: thoger | Owner: pam-developers@…
Type: defect | Status: new
Priority: minor | Component: modules
Version: | Keywords:
Blocked By: | Blocking:
---------------------+------------------------------
pam_timestamp module supports `timestampdir` option, which is not properly
mentioned in the documentation / man page for the module. The only
mention is:
When an application opens a session using
<emphasis>pam_timestamp</emphasis>,
a timestamp file is created in the <emphasis>timestampdir</emphasis>
directory
for the user.
but it is not listed in SYNOPSIS or OPTIONS sections.
--
Ticket URL: <https://fedorahosted.org/linux-pam/ticket/33>
linux-pam <http://fedorahosted.org/linux-pam>
The Linux-PAM (Pluggable Authentication Modules) project
9 years, 1 month