Opened 11 years ago

Closed 5 years ago

#5576 closed defect (fixed)

Gadu-Gadu via proxy (SOCKS5)

Reported by: mwte Owned by: tomkiewicz
Milestone: 3.0.0 Component: Gadu-Gadu
Version: 2.4.1 Keywords: proxy socks5
Cc:

Description

Pidgin does not work via proxy (SOCKS5).

There is no problems with SOCKS5 on other protocols (Jabber etc). It is just GG. Any ideas?

Same problem with Adium: #a9943

Attachments (1)

2008-04-19.log (6.9 KB) - added by mwte 11 years ago.
Debug log

Download all attachments as: .zip

Change History (8)

comment:1 in reply to: ↑ description Changed 11 years ago by mwte

Fixed link: #a9443

Changed 11 years ago by mwte

Debug log

comment:2 Changed 11 years ago by datallah

  • Summary changed from Pidgin via proxy (SOCKS5) to Gadu-Gadu via proxy (SOCKS5)

comment:3 Changed 10 years ago by datallah

I can recreate this.

This is because the gg prpl doesn't use the libpurple core connection code - instead it code in libgadu makes the connection. There is some attempt to import the libpurple proxy settings into libgadu, but that appears to only support HTTP proxies.

It looks like fixing this correctly will require refactoring libgadu to support using external connection handling code.

comment:4 Changed 7 years ago by tomkiewicz

  • Keywords gadu-gadu removed
  • Owner changed from bartosz to tomkiewicz

comment:5 Changed 5 years ago by tomkiewicz

Update: libgadu 1.12.0-rc1 supports external connection functions and gg prpl uses it, when compiled with GGP_ENABLE_GG11 macro set to 1. When the final libgadu 1.12.0 comes out, gg prpl should support any type of TCP proxy out of the box.

However, HTTP services (public directory, password change) still doesn't use these. It's a TODO thing.

comment:6 Changed 5 years ago by tomkiewicz

  • Milestone set to 3.0.0

comment:7 Changed 5 years ago by Tomasz Wasilczyk <twasilczyk@…>

  • Resolution set to fixed
  • Status changed from new to closed

(In [8db516861567]):
Don't mess with proxy, when we use GG11 - it's handled by libpurple. Fixes #5576

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!