Package: oath-toolkit / 2.6.1-1.4
Patch seriesview the series file
|gtkdocize.patch | (download)||
227 134 + 93 - 0 !
"gtkdocize --copy" with gtk-doc-tools 1.28-1 Fixes FTBFS with gtk-doc-tools >= 1.26.
|new glibc check.patch | (download)||
4 2 + 2 - 0 !
check _io_eof_seen instead of _io_ftrylockfile Needed to get fseeko.c to build with glibc 2.28. Inspired by https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=4af4a4a71827c0bc5e0ec67af23edef4f15cee8e.
|0001 fail gracefully for missing users.patch | (download)||
[patch] fail gracefully for missing users when the pam module is enabled, it forces *all* users to immediately start using OATH, or they can't login at all. a more progressive approach would seem more reasonable to me, especially since each user need to get an admin user to update the central file for them. this patch adds an early check to the users file and makes sure the user exists before prompting for a password. if the user is missing, it exits early with a standard error code (PAM_USER_UNKNOWN) which can then be ignored in the PAM configuration (as shown in the README file). this leaves the policy decision up to the admin (and defaults to "fail closed"). if the user is present, the code path remains the same except the usersfile is scanned twice, which may be a performance penalty on very slow filesystems or very large files. the only workaround I can think of for this would be to load the whole file into memory, but this could have significant memory impact on large files. the function used (`oath_authenticate_usersfile`) is a little overkill as it actually goes and tries to authenticate the user with an empty password. this is harmless because the file isn't updated if the OTP is incorrect and because no warning is sent to syslog. a possible improvement on this would be to have a warning shown to the user inciting them to configure OATH or to warn them about a possible typo in their username before they enter their regular passphrase