[Thinkfinger-devel] T60 - Thinkfinger Alarm Clock message crashes terminal

[Filipe Miranda]

Hello,

I have a thinkpad T60 S/N:L1-2555B and after installing thinkfinger version
thinkfinger-0.2.2-4.fc6, registered my finger print and added the following
line to the /etc/pam.d/system-auth:
auth required pam_env.so
auth sufficient pam_thinkfinger.so #added line
auth sufficient pam_unix.so nullok try_first_pass
auth requisite pam_succeed_if.so uid >= 500 quiet
auth required pam_deny.so

the finger print recognition works great!!
The problem that I noticed is, if I use sudo, or su or ay type of
authentication when using for example the gnome-terminal, I get the mesage
after a while : Alarm Clock and my terminal crashes.

Any idea why this happen. I noticed that this onl happens when I
authenticate using the thinkfinger module.

regards,

[Timo Hoenig]

Hi Filipe,

Sorry for the lag.

Post by Filipe Miranda
I have a thinkpad T60 S/N:L1-2555B and after installing thinkfinger
version thinkfinger-0.2.2-4.fc6, registered my finger print and added
auth required pam_env.so
auth sufficient pam_thinkfinger.so #added line
auth sufficient pam_unix.so nullok try_first_pass
auth requisite pam_succeed_if.so uid >= 500 quiet
auth required pam_deny.so
the finger print recognition works great!!

Great!

Post by Filipe Miranda
The problem that I noticed is, if I use sudo, or su or ay type of
authentication when using for example the gnome-terminal, I get the
mesage after a while : Alarm Clock and my terminal crashes.

Uh? That sounds scary :-) Can you please verbose about what
distribution you're using?

Post by Filipe Miranda
Any idea why this happen. I noticed that this onl happens when I
authenticate using the thinkfinger module.

No idea, never heard anything similar yet.

Timo

[Filipe Miranda]

Hello Timo,

Thanks for the response.
I'm using Fedora Core 6 with the latest updates as March 10.

The problem with the Alarm Clock I think it is not directely related to the
thinkfinger software.
I noticed that it ONLY happened when I used the sudo option as: "sudo su -"

Does the thinkfinger generates a tokes that is valid for some time and then
it expires?

The Alarm Clock messages would appear in my terminal (pratically killing it)
after 5-10 min after I authenticated into a terminal user using "sudo su -"

As a workaround I disabled the password check needed for my user when
calling sudo, and the message does not appear anymore: (visudo)
username ALL=(ALL) NOPASSWD: ALL

I dont know if this is a characteristic of the pam + sudo or if its a
characteristic of thinkfinger + sudo...

Any ideas?

Post by Timo Hoenig
Hi Filipe,
Sorry for the lag.

Post by Filipe Miranda
I have a thinkpad T60 S/N:L1-2555B and after installing thinkfinger
version thinkfinger-0.2.2-4.fc6, registered my finger print and added
auth required pam_env.so
auth sufficient pam_thinkfinger.so #added line
auth sufficient pam_unix.so nullok try_first_pass
auth requisite pam_succeed_if.so uid >= 500 quiet
auth required pam_deny.so
the finger print recognition works great!!

Great!

Post by Filipe Miranda
The problem that I noticed is, if I use sudo, or su or ay type of
authentication when using for example the gnome-terminal, I get the
mesage after a while : Alarm Clock and my terminal crashes.

Uh? That sounds scary :-) Can you please verbose about what
distribution you're using?

Post by Filipe Miranda
Any idea why this happen. I noticed that this onl happens when I
authenticate using the thinkfinger module.

No idea, never heard anything similar yet.
Timo

[Kilian CAVALOTTI]

Hi all,

Post by Filipe Miranda
The problem that I noticed is, if I use sudo, or su or ay type of
authentication when using for example the gnome-terminal, I get the
mesage after a while : Alarm Clock and my terminal crashes.

Uh? That sounds scary Can you please verbose about what
distribution you're using?

Post by Filipe Miranda
Any idea why this happen. I noticed that this onl happens when I
authenticate using the thinkfinger module.

No idea, never heard anything similar yet.

I can confirm the exact same behaviour on a Gentoo distribution. The 'Alarm
clock' thing only appears when using sudo and the fingerprint reader. It looks
to me like a kill -14 (SIGALRM), but I have no idea where it could come from.

Cheers,