seahorse passphrase dialogs don't accept input
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
scim (Ubuntu) |
Fix Released
|
Low
|
Rolf Leggewie | ||
Bug Description
Binary package hint: seahorse
I ran into a problem (already the second time) in Intrepid Ibex Beta. It is a fresh install and I installed all upgrades. Until recently the problem didn't occur. However, apparently since enabling installation of "proposed updates" the problem is there again.
Using Seahorse - no matter if directly for key management or through the Enigmail extension to Thunderbird when encrypting email - the pass-phrase request dialogue doesn't accept any input. Whenever I want to sign an email or encrypt it, Enigmail will ask for the pass-phrase with a dialogue. I made sure the cursor is in the textfield and typed the correct pass-phrase. However, there is no visual feedback in the dialogue anymore. The Enter key is recognized, though. No matter what I input, the pass-phrase is rejected and a new dialogue pops up stating that the pass-phrase was incorrect. This happens another time again until Seahorse gives up on me.
Same situation without using Thunderbird when directly opening Seahorse and changing settings for a particular key.
I'm sure the pass-phrase is correct. I faced this problem before with an old key. I thought that maybe I just cannot remember the password so I revoked the key and created a new one. Also that didn't work. So I reinstalled Ubuntu from the Intrepid Beta ISO and it worked.
Since installing updates from the "proposed" set some days ago the bug appeared again. At least I assume that there is a connection. I made a simple screencast to demonstrate the odd behaviour which I attached below.
seahorse:
Installed: 2.24.0-0ubuntu1
Candidate: 2.24.0-0ubuntu1
Version table:
*** 2.24.0-0ubuntu1 0
500 http://
100 /var/lib/
seahorse-plugins:
Installed: 2.24.0-0ubuntu1
Candidate: 2.24.0-0ubuntu1
Version table:
*** 2.24.0-0ubuntu1 0
500 http://
100 /var/lib/
I would appreciate any idea that could help fixing this as this renders everything related to encryption totally useless. I'm not sure if this poses a specific security threat but definitely has a big impact on security when you cannot use any keys managed by Seahorse any more.
Changed in seahorse: | |
status: | New → Confirmed |
security vulnerability: | yes → no |
same problem here!