← Back to team overview

gwibber-bugs team mailing list archive

[Bug 922477] Re: Status.net backend does not accept self-signed ssl

 

Thank you for taking the time to report this bug and helping to make Ubuntu better. 
nice idea  marking wishlist,,

** Changed in: gwibber (Ubuntu)
       Status: New => Confirmed

** Changed in: gwibber (Ubuntu)
   Importance: Undecided => Wishlist

** Also affects: gwibber
   Importance: Undecided
       Status: New

** Changed in: gwibber
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Gwibber
Bug Heros, which is subscribed to Gwibber.
https://bugs.launchpad.net/bugs/922477

Title:
  Status.net backend does not accept self-signed ssl

Status in Gwibber:
  New
Status in “gwibber” package in Ubuntu:
  Confirmed

Bug description:
  I have my own status.net instance running, but it uses a self-signed SSL certificate.
  Gwibber does not allow me to authorize over this SSL link, only plain http (which is insecure).

  Note that this affects both the stable Ubuntu releases as the upcoming
  precise release.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gwibber-service-statusnet 3.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-10.18-generic 3.2.1
  Uname: Linux 3.2.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  Date: Fri Jan 27 09:16:55 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110824)
  PackageArchitecture: all
  SourcePackage: gwibber
  UpgradeStatus: Upgraded to precise on 2012-01-22 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gwibber/+bug/922477/+subscriptions