I have recently studied the effects of some 'sudo'-related bugs. Have you been able to reproduce this lately?
Are you completely sure that you had not given your password to any other application before? (You didn't e.g. change your computer's clock or use some automated program to install a new application, or do anything that could require you to write your password? Maybe used Synaptic or another application installer or give your sudo password in an earlier terminal instance?)
The reason I ask: If you had given your password somewhere, anywhere, during the 15 minutes prior to this, the mechanism caching the sudo tty_tickets could easily be responsible for this behaviour.
Also, you mention 20 minutes above, but you also mention trying this a few times with a few minutes in between. (Doing this a few times with a few minutes in between renews the timestamp each time.) If you're sure that you had 20 minutes time between two consecutive attempts (>15 min), or you haven't changed your computer's clock, this may then be something different.
Hello.
I have recently studied the effects of some 'sudo'-related bugs. Have you been able to reproduce this lately?
Are you completely sure that you had not given your password to any other application before? (You didn't e.g. change your computer's clock or use some automated program to install a new application, or do anything that could require you to write your password? Maybe used Synaptic or another application installer or give your sudo password in an earlier terminal instance?)
The reason I ask: If you had given your password somewhere, anywhere, during the 15 minutes prior to this, the mechanism caching the sudo tty_tickets could easily be responsible for this behaviour.
Also, you mention 20 minutes above, but you also mention trying this a few times with a few minutes in between. (Doing this a few times with a few minutes in between renews the timestamp each time.) If you're sure that you had 20 minutes time between two consecutive attempts (>15 min), or you haven't changed your computer's clock, this may then be something different.