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

2012-08-07 Thread Guy Van Sanden
Reopening, this is still an issue, I provided all requested information

** Changed in: gwibber (Ubuntu)
   Status: Expired = Confirmed

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

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

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/ubuntu/+source/gwibber/+bug/922477/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2012-08-05 Thread Launchpad Bug Tracker
[Expired for gwibber (Ubuntu) because there has been no activity for 60
days.]

** Changed in: gwibber (Ubuntu)
   Status: Incomplete = Expired

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

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

Status in “gwibber” package in Ubuntu:
  Expired

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/ubuntu/+source/gwibber/+bug/922477/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2012-06-06 Thread Guy Van Sanden
Please reopen, this is still an issue and I provided all data

** Changed in: gwibber (Ubuntu)
   Status: Expired = Incomplete

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

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

Status in “gwibber” package in Ubuntu:
  Incomplete

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/ubuntu/+source/gwibber/+bug/922477/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2012-06-05 Thread Launchpad Bug Tracker
[Expired for gwibber (Ubuntu) because there has been no activity for 60
days.]

** Changed in: gwibber (Ubuntu)
   Status: Incomplete = Expired

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

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

Status in “gwibber” package in Ubuntu:
  Expired

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/ubuntu/+source/gwibber/+bug/922477/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2012-04-06 Thread Bilal Shahid
forget about my last comment..
Thank you for taking the time to report this bug and helping to make Ubuntu 
better, 
* can you reproduce it ? 
* if so than which version are you on ?

** No longer affects: gwibber

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

** Changed in: gwibber (Ubuntu)
   Status: Confirmed = Incomplete

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

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

Status in “gwibber” package in Ubuntu:
  Incomplete

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/ubuntu/+source/gwibber/+bug/922477/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2012-04-06 Thread Guy Van Sanden
Can reproduce it 100%
Versions in both Ubuntu 11.10 and 12.04 tested and both don't handle SSL

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

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

Status in “gwibber” package in Ubuntu:
  Incomplete

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/ubuntu/+source/gwibber/+bug/922477/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2012-02-22 Thread Bilal Shahid
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 Desktop
Packages, which is subscribed to gwibber in Ubuntu.
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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2012-01-27 Thread Guy Van Sanden
-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gwibber in Ubuntu.
https://bugs.launchpad.net/bugs/922477

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

Status in “gwibber” package in Ubuntu:
  New

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/ubuntu/+source/gwibber/+bug/922477/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp