{"push_id":1100037833,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"f35989829934bbfdde15de22aacb2970668d4d60","before":"c9ed7bd3ee9332ee5e808a44d32f8be9cc155484","commits":[{"sha":"f35989829934bbfdde15de22aacb2970668d4d60","author":{"email":"a24afe857bacd94516c4980497275e699229cb8b@google.com","name":"Thomas Habets"},"message":"Improve PAM API conformance by using pam_get_user\n\nThe pam_start(3) manual page (on Debian 8) says:\n\n\"The user argument can specify the name of the target user and will be\nstored as PAM_USER item. If the argument is NULL, the module has to ask\nfor this item if necessary.\"\n\nThe manual page for pam_get_item(3) (current mechanism which the module\nuses to obtain the user name) says:\n\n\"If a service module wishes to obtain the name of the user, it should\nnot use this function, but instead perform a call to pam_get_user(3).\"\n\nThis patch will fix the situation whereby PAM_USER isn't set at the\ntime that the module is invoked (e.g. because it is the first PAM\nmodule in the stack on the system in question, and the application\nwhich is attempting authentication via PAM has (legitimately) not set\nthe user in it's call to pam_start().\n\nCurrent behaviour breaks when pam_google_authenticator is used with\nopenvpn's openvpn-plugin-auth-pam.so, and also xrdp:\n\nhttps://github.com/google/google-authenticator/issues/361\n\nAuthor: Tim Small <tim@seoss.co.uk>","distinct":true,"url":"https://api.github.com/repos/google/google-authenticator/commits/f35989829934bbfdde15de22aacb2970668d4d60"}]}