Issue 241 in google-authenticator: Unable to login to Servers after few days of enabling Google Auth.

[google-aut...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 241 by hamlind...@gmail.com: Unable to login to Servers after few
days of enabling Google Auth.
http://code.google.com/p/google-authenticator/issues/detail?id=241

Hey,

I had installed a google auth. few days back on two of my servers. My
servers have multiple user accounts, each one of them have configured
Google auth. For a few days everything worked fine. Everyone was able to
login. But suddenly today morning none of us were able to login via SSH.

What steps will reproduce the problem?
Not sure how to reproduce the the problem.

What is the expected output? What do you see instead?
The output displayed on the putty screen:
Using keyboard-interactive authentication.
Verification code:
Access denied
Using keyboard-interactive authentication.
Password:

What version of the product are you using? On what operating system?
Debian Squeeze 6.0

Please provide any additional information below.
The following is a snippet of the log in auth.log:
Jan 17 10:11:35 debian sshd(pam_google_authenticator)[1930]: Invalid
verification code
Jan 17 10:11:35 debian sshd(pam_google_authenticator)[1930]: Failed to
update secret file "/home/user/.google_authenticator"
Jan 17 10:11:37 debian sshd[1927]: error: PAM: Cannot make/remove an entry
for the specified session for user from 10.0.0.32

The google authenticator file is present in the home directories of the
users. No hard-disk encryption is enabled. SELinux is disabled.

I have checked the server time & the time on the mobiles is similar less
than 60secs delay.

Any help/pointers would be highly appreciated.

[google-aut...@googlecode.com]

Comment #1 on issue 241 by hamlind...@gmail.com: Unable to login to Servers

after few days of enabling Google Auth.
http://code.google.com/p/google-authenticator/issues/detail?id=241

I've added noskewadj in /etc/pam.d/sshd

auth required pam_google_authenticator.so noskewadj

But I still face this issue after a few days.

When I'm unable to login, even the emergency scratch codes dont work.

[google-aut...@googlecode.com]

Comment #2 on issue 241 by bdavi...@gmail.com: Unable to login to Servers

after few days of enabling Google Auth.
http://code.google.com/p/google-authenticator/issues/detail?id=241

Hi,

i have exactly the same problem.
My operation system is CentOS 6.4.

My emergency scratch codes works, but my verification code doesn't work.

Do you have any idea about this ?

Regards,
David

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[google-aut...@googlecode.com]

Comment #3 on issue 241 by bdavi...@gmail.com: Unable to login to Servers

after few days of enabling Google Auth.
http://code.google.com/p/google-authenticator/issues/detail?id=241

Ok i solve my problem now.

On google authenticator on my smartphone i didn't have the same account
name as on my centos server.