Facebook certificate is untrusted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Empathy |
New
|
Undecided
|
Unassigned | ||
Gwibber |
New
|
Undecided
|
Unassigned | ||
ca-certificates |
Confirmed
|
Undecided
|
Unassigned | ||
telepathy-gabble |
Invalid
|
Undecided
|
Unassigned | ||
gwibber (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
telepathy-gabble (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gwibber
I heard reports like this from other project (e.g. iPhone SDK), so assume it is not a genuine issue with the login process. I am using 10.10, totally up-to-date (Gwibber 2.32.2). I see a dialogue like this when enabling the FB account:
"This connection is untrusted. Would you like to continue anyway?
The identity provided by the chat server cannot be verified.
The certificate is self-signed.
"
Sometimes this pops up twice (I don't tick "remember this choice....". As a side point, the dialogue vanishes if you move away from it (making it hard to copy & paste the content here). Gwibber is still waiting for my response but I can't Alt-Tab back to it. The certificate has SHA-1 fingerprint:
22 E5 0E EE AF 2D AF 8E 44 03 77 19 6C 4D 95 73 4D EE 94 D9
It is within the valid date range, and does not actually appear to be self-signed: DigiCert is the issuer. There is no OU for the certificate.
Related branches
- Jamie Strandboge: Disapprove
- Ubuntu branches: Pending requested
-
Diff: 743 lines (+705/-2)3 files modifieddebian/changelog (+9/-0)
debian/config (+2/-2)
mozilla/certdata.txt (+694/-0)
Changed in telepathy-gabble: | |
status: | New → Invalid |
Changed in ca-certificates: | |
status: | New → Confirmed |
I've had this happening to me for a while and I'm glad to see someone else has reported it. It now makes it far less likely someone is reading my conversations.
Just for posterity, I also have the same certificate: SHA1 is 22 E5 0E EE AF 2D AF 8E 44 03 77 19 6C 4D 95 73 4D EE 94 D9