desktop-packages team mailing list archive

[Ron Campbell <746973@xxxxxxxxxxxxxxxxxx>]

*** This bug is a duplicate of bug 742889 ***
    https://bugs.launchpad.net/bugs/742889

Has anyone actually checked the validity of the certificate?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to telepathy-gabble in Ubuntu.
https://bugs.launchpad.net/bugs/746973

Title:
  Facebook certificate is untrusted

Status in Common CA certificates:
  Confirmed
Status in Chat app, and Telepathy user interface:
  New
Status in Gwibber:
  New
Status in Jabber/XMPP connection manager:
  Invalid
Status in “gwibber” package in Ubuntu:
  Invalid
Status in “telepathy-gabble” package in Ubuntu:
  Invalid

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ca-certificates/+bug/746973/+subscriptions