Description of problem: See screen-shots maybe gpg key isn't supported anymore? Version-Release number of selected component (if applicable): How reproducible: every time on more than one box Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
Created attachment 5586 [details] Screenshot 1
Created attachment 5587 [details] Screenshot2
with the rpm or mozilla extension ? (you should try the last)
with rpm
CC: (none) => doktor5000, fundawang
Whiteboard: (none) => cauldron too
Did you try the upstream extension as previously suggested? https://www.enigmail.net/download/release/1.7/enigmail-1.7.2-tb+sm.xpi Also see https://www.enigmail.net/documentation/advanced.php#debug and https://www.enigmail.net/forum/viewtopic.php?f=10&t=289 and https://www.enigmail.net/support/bugs.php on how to report this upstream. Please also check https://www.enigmail.net/support/troubles.php#flowed And definitely enable the enigmail console to copy the resulting commands here instead of screenshots. menu Enigmail -> Troubleshooting -> enable console.
Version: 4 => CauldronWhiteboard: cauldron too => MGA4TOOSeverity: major => normal
1. I am not going to try the upstream extension on a working box. Those are usually already outdated when the next thunderbird upgrade comes. I'll try it on cauldron Oh, I see this package has no maintainer. It seems, It only has a problem with certain signatures, including mine. So let's see if upstream fixes it. BTW, this doesn't exits: menu Enigmail -> Troubleshooting -> enable console
(In reply to Thomas Spuhler from comment #6) > 1. I am not going to try the upstream extension on a working box. Those are > usually already outdated when the next thunderbird upgrade comes. > I'll try it on cauldron Are you kidding? The upstream extension will always be at the most recent version, as we need to update it manually with each update (and sometimes packagers forget this) which leads to outdated packaged enigmail in our repos. But feel free to ignore suggestions that could help you fix your problem. > So let's see if upstream fixes it. Sure, they will automagically fix something which they don't even know about. > BTW, this doesn't exits: > menu Enigmail -> Troubleshooting -> enable console Did you enable the enigmail log as described in the first link https://www.enigmail.net/documentation/advanced.php#debug ? Afterwards there's an additional menu entry in Enigmail menu (previously that was just a translation from my german enigmail) -> Debugging options -> View Console which will show all the commands that enigmail will run, in plaintext . As nobody else confirmed this yet, setting status keyword appropriately.
Status: NEW => UNCONFIRMEDEver confirmed: 1 => 0
why write this long comment? Please test it on your box. I can send you a signed e-mail and if it shows on your box as valid signature than I have a problem.
(In reply to Thomas Spuhler from comment #8) > why write this long comment? Please test it on your box. I can send you a > signed e-mail and if it shows on your box as valid signature than I have a > problem. This is still open. Installing version 1.8.1 solved the problem. Why do we still have %define enigmail_version 1.7.2
Status: UNCONFIRMED => ASSIGNEDAssignee: bugsquad => doktor5000Ever confirmed: 0 => 1
1.7.2 from the repos works fine here, just created a keypair, signed+encrypted a mail, sent it to me and entered my private key. Correctly decrypted, and signature checks out OK. Same for a mail that is only signed via enigmail. As you don't even mention your exact use case (signing mail, encrypting mail, signing+encrypting, using S/MIME or PGPG, inline PGP or not) and as you didn't provide any logs or debug information won't continue further. We still have 1.7.2 because nobody changed that yet. You have SVN access, you know how it works. But as it works here with 1.7.2 your issue is probably different. In the future, please refrain from assigning bugs to others _and_ changing the status to Assigned. This is only intended for the assignee himself to indicate he's actively working on it.
Status: ASSIGNED => NEWAssignee: doktor5000 => bugsquad
I can send you a signed e-mail and it should say the signature is not valid with 1.7.2. This was on two boxes.
Created attachment 6310 [details] prior to importing public key, also showing signature details, with 1.7.2 prior to importing public key, also showing signature details, with 1.7.2
Created attachment 6311 [details] after importing key, without trusting signature, with 1.7.2 after importing key, without trusting signature, with 1.7.2
See my two screenshots. Compare it to yours https://bugs.mageia.org/attachment.cgi?id=5586 and you will see that you haven't imported your public key yet or there was an issue with it, maybe wrong permissions or wrong keyserver is set or one that doesn't have your public key. That's why I mentioned you need to provide some logs.
I am aware of the difference. The question is why does it not find the public signature that is has already downloaded. I am glad to send you the logs, if you tell me where to find them. I am not very familiar with Thunderbird. There is nothing in the journal, so I need to turn them on somewhere. BTW, I removed einigmail-1.8.1 and installed 1.7.2 using urmi and I am back to the reported problem. Since 1.8.1 and kmail knows the public key, it's clearly available. If you look at my key, it's a little complicated, it has two e-mail addresses and a picture.
See comment 5 and comment 7 And don't send the logs to me, that's what bugzilla is for.
(In reply to Florian Hubold from comment #16) > See comment 5 and comment 7 > And don't send the logs to me, that's what bugzilla is for. We talked enough. 1.8.1 from upstream works here. I don't have time to further debug it. I am going to upgrade it per comment 10 in svn and when the next security update comes along it will be pushed.
fixed in SVN by upgrading enigmail to vers. 1.8.2 Tested locally and it fixes the bug. I am not going to push the build, can be done by next upgrade of thunderbird.
Status: UNCONFIRMED => RESOLVEDResolution: (none) => FIXED