Created attachment 941897 [details] Details of Certificate Description of problem: I want to connect to ***@dukgo.com XMPP/Jabber account. I can't. I have an error in verification/authentication phase. Empathy is default client of IM in Fedora 21 Workstation so I expected to work well with this popular XMPP service. Version-Release number of selected component (if applicable): Fedora 21 Workstation Alpha with Gnome 3.13/3.14 yum info empathy Version : 3.12.6 Wydanie : 1.fc21 yum info telepathy-gabble.x86_64 Wersja/version : 0.18.2 Wydanie : 3.fc21 yum info telepathy-salut.x86_64 Wersja/version : 0.8.1 Wydanie : 7.fc21 How reproducible: Always Steps to Reproduce: 1. Create new account via www on https://duck.co/ or via Pidgin on dukgo.com 2. Try to connect using Empathy Actual results: Uwierzytelnianie nie powiodło się - verification/authentication failed. Expected results: Succesful log in to account. Additional info: I was using Fedora 20 Alpha year ago too, and I had the same error. Pidgin works well with this account in Fedora. Empathy works well with less secure Yandex XMPP server (ya.ru). This is a screen with configuration from Pidgin. Works well: http://s11.postimg.org/5f978gq0j/Pidgin_Dukgocom.png This is a screen from Empathy. It can't log in. http://s9.postimg.org/ho95ncwhb/Empathy_Dukgocom.png I can connect using Empathy on Debian Wheezy (SteamOS based on Debian + Debian repo). When Empathy is logging in then it shows this window, but after accepting it connects and works well: http://s1.postimg.org/3xbc8twyn/Certificate_Warning.jpg http://s1.postimg.org/n3ojc0dgf/Certificate_Warning2.jpg This is text from window: duck.co Identity: duck.co Verified by: COMODO High-Assurance Secure Server CA Expires: 02.12.2014 Subject Name C (Country): US 2.5.4.17: #13053139343630 ST (State): Pennsylvania L (Locality): Paoli STREET (Street): 20 Paoli Pike O (Organization): DuckDuckGo OU (Organizational Unit): Multi-Domain SSL CN (Common Name): duck.co Issuer Name C (Country): GB ST (State): Greater Manchester L (Locality): Salford O (Organization): COMODO CA Limited CN (Common Name): COMODO High-Assurance Secure Server CA Issued Certificate Version: 3 Serial Number: 1C 80 82 CB D0 B1 CF A0 1D 24 4C 89 DC 61 90 AC Not Valid Before: 2013-12-02 Not Valid After: 2014-12-02 Certificate Fingerprints SHA1: 08 1F 7C 20 0A 80 48 34 06 01 F0 72 5E AA AA 0E 38 28 5C E4 MD5: DC 86 CB 79 BD 42 E6 76 4F 80 3D AD A5 C5 A4 94 Public Key Info Key Algorithm: RSA Key Parameters: 05 00 Key Size: 4096 Key SHA1 Fingerprint: 3A E3 5A 2F 69 60 B3 26 77 69 F8 C6 6B DD 51 7C 64 46 3E 10 Public Key: 30 82 02 0A 02 82 02 01 00 D8 87 BA C6 75 AF 65 0D E1 6E 35 DC 04 B7 89 62 54 F3 F6 30 CB D7 24 DF 7E AC 68 D9 97 08 B3 6B 8C 98 74 7E C6 13 D3 52 94 32 CC 39 9B 5D 08 D1 6C 61 5F 8C 05 92 4F 86 FD 66 4F D7 41 7E 57 9A 78 0F 86 1D 1B CB 64 00 6B 88 4A 81 EA CF 17 3E 12 7A E3 42 5C 6F CF 48 37 F7 37 7B 3D ED 10 85 81 6A 76 59 8F 02 BB AF 84 78 A7 2A 2C FB BF 88 DE D1 36 67 EF A1 67 26 6A 42 B0 C3 3A 26 F4 8E 03 78 B1 F8 74 88 FB 5B 44 1C 59 D7 84 E0 A4 DD 21 41 5B 2F B3 B7 CF DF B2 B6 80 2A 61 80 19 8C 16 72 04 98 AF 5E 85 4C B6 34 1F 32 6B 5B C3 F2 24 C2 01 24 38 93 EC F4 E6 D0 2C 0C 6C E2 56 A2 B6 69 91 C9 D6 90 32 0B DA 8C C2 A1 22 D2 94 9D D5 E7 8A 2A D9 73 A4 C5 8B 96 8F 30 D2 EB 31 B8 9C AF 24 9F EB C3 48 DD C1 24 F1 9C D0 9D C3 17 23 F5 14 13 36 D2 C4 5E E8 B7 26 12 C0 3F E3 56 65 54 F1 DD 17 CF 38 BC AB 24 FC 16 7B A3 F5 31 B9 E6 15 88 EC 59 58 C0 C5 8A CB C4 01 E5 0C 68 5B 24 56 34 0B F6 69 F7 D1 F5 F6 97 3F C1 E5 2A FF C3 9E 02 33 E3 CD 8E E4 5C 23 CD 9E 3F E5 77 1F 80 68 25 71 87 F3 96 FA D3 1E 32 D4 5B DF 78 B3 25 38 96 9B 75 0E 47 1F 12 1F 34 39 7E 72 D0 3F E7 F0 19 F0 88 6E C5 B0 47 5F 87 E3 04 7F F5 15 BC 35 E8 1D 37 0B E9 0B 19 5D D7 E8 7C 71 13 D7 40 7E 0D F0 61 E4 16 D9 B9 D6 34 D6 5D AD 61 53 9D 4F 10 F1 AB 73 D0 A4 4D 69 88 0F 4F A3 B8 59 F7 F4 4B 45 25 92 97 97 2B 26 3C 7F A1 A9 4C D5 43 A6 09 30 57 38 CC 59 F8 13 3A 93 5F 33 26 13 02 31 DF FE E8 67 9C 43 42 86 62 F0 8B FC 9A 06 00 F5 8F 50 19 58 A9 D0 A6 0E A6 5A 8B EB 08 47 18 6A E9 FB 1C BD 68 2A 2D 5A 87 78 2C C3 D7 47 B4 3A F7 41 85 BD 69 D0 32 E0 EA 14 8C 61 63 02 03 01 00 01 Extension Identifier: 2.5.29.35 Value: 30 16 80 14 3F D5 B5 D0 D6 44 79 50 4A 17 A3 9B 8C 4A DC B8 B0 22 64 6B Critical: No Subject Key Identifier Key Identifier: 2C 8A 2E 9D 01 95 CB 8F 50 3B 7C 57 3C CB 99 7B 30 B7 65 18 Critical: No Key Usage Usages: Digital signature Key encipherment Critical: Yes Basic Constraints Certificate Authority: No Max Path Length: Unlimited Critical: Yes Extended Key Usage Allowed Purposes: Server Authentication Client Authentication Critical: No Extension Identifier: 2.5.29.32 Value: 30 47 30 3B 06 0C 2B 06 01 04 01 B2 31 01 02 01 03 04 30 2B 30 29 06 08 2B 06 01 05 05 07 02 01 16 1D 68 74 74 70 73 3A 2F 2F 73 65 63 75 72 65 2E 63 6F 6D 6F 64 6F 2E 63 6F 6D 2F 43 50 53 30 08 06 06 67 81 0C 01 02 02 Critical: No Extension Identifier: 2.5.29.31 Value: 30 46 30 44 A0 42 A0 40 86 3E 68 74 74 70 3A 2F 2F 63 72 6C 2E 63 6F 6D 6F 64 6F 63 61 2E 63 6F 6D 2F 43 4F 4D 4F 44 4F 48 69 67 68 2D 41 73 73 75 72 61 6E 63 65 53 65 63 75 72 65 53 65 72 76 65 72 43 41 2E 63 72 6C Critical: No Extension Identifier: 1.3.6.1.5.5.7.1.1 Value: 30 72 30 4A 06 08 2B 06 01 05 05 07 30 02 86 3E 68 74 74 70 3A 2F 2F 63 72 74 2E 63 6F 6D 6F 64 6F 63 61 2E 63 6F 6D 2F 43 4F 4D 4F 44 4F 48 69 67 68 2D 41 73 73 75 72 61 6E 63 65 53 65 63 75 72 65 53 65 72 76 65 72 43 41 2E 63 72 74 30 24 06 08 2B 06 01 05 05 07 30 01 86 18 68 74 74 70 3A 2F 2F 6F 63 73 70 2E 63 6F 6D 6F 64 6F 63 61 2E 63 6F 6D Critical: No Subject Alternative Names DNS: duck.co DNS: dukgo.com Critical: No Signature Signature Algorithm: SHA1 with RSA Signature Parameters: 05 00 Signature: 6A D7 A4 F5 91 C7 75 0B DD 40 A9 EE DE 61 E2 C3 2C F3 82 DF 76 48 EA BA D5 8D 43 EF 3C 07 E5 38 E8 0C 1B A5 C7 E4 1E 11 30 69 31 44 C8 24 9F 56 A6 D6 F6 D8 D8 EE 09 37 38 85 C5 20 56 1B 1E 71 99 A0 1A F0 EC 03 61 B6 33 A1 77 51 C6 3F 16 1A 97 3B DF 59 F6 37 08 22 2E B6 2D E0 3C 6D 33 F7 88 CC 6C DD 1A 87 5E EA 84 6F 5D 3F EC 69 2A 51 54 35 C5 91 97 34 9C 52 1D 6C 6D 41 75 4F 7F 8C 6D 02 34 15 BF A5 56 EB 20 89 09 E2 7A 06 B2 AD C7 4B 1D C3 42 3F C9 08 73 82 E6 80 DA B7 13 C4 81 FC C4 CB 62 DC 65 43 AF BD 2C 64 19 CA 08 AB D4 20 9B 34 A5 56 3D 8F 8D 49 8B C9 1C 54 62 46 CE F3 21 93 8E 1C 97 F4 45 68 BD 5A 4E 69 EF 5E BE 7C 01 FB AC 68 4A C7 C2 1F 30 6A 97 59 D6 BA 9F 8D AF F1 84 B0 60 1B 96 EC 6F 92 97 8C 2F B6 16 51 66 FB 39 34 A3 0A 98 65 E0 8C 56 30 31 53
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.