After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 331607 - Add proxy support
Add proxy support
Status: RESOLVED WONTFIX
Product: xchat-gnome
Classification: Other
Component: general
unspecified
Other Linux
: High enhancement
: .30
Assigned To: xchat-gnome maintainers
xchat-gnome maintainers
gnome[unmaintained]
: 596046 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-02-17 21:04 UTC by Guillaume Desmottes
Modified: 2019-02-23 02:49 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Guillaume Desmottes 2006-02-17 21:04:52 UTC
Original report: https://launchpad.net/distros/ubuntu/+source/xchat-gnome/+bug/31812

It will be good to use GNOME proxy settings.
Comment 1 Justin Georgeson 2006-02-17 23:14:47 UTC
While logically it makes sense that a GNOME app acknowledges the global settings, I would like to have an option in xchat-gnome to specify proxy settings local to the app. On some networks I like to proxy web/im/irc through an SSH tunnel to a machine I control, so I can be certain none of it can be snooped. But I don't want everything to default to running through that proxy, just the small set of apps I explicitly point at it. The base x-chat supports proxy settings, so it should be trivial to incorporate into xchat-gnome.
Comment 2 Andrew D. 2006-04-15 02:20:31 UTC
I use Tor to mask my IP address, and the only way I can get xchat-gnome to run using Tor is to either configure the entire system to use it or uninstall xchat-gnome, install xchat, configure it in xchat, then uninstall xchat and reinstall xchat-gnome. Either way is a pain in the butt.

A section in the xchat-gnome options devoted to proxies, or at least a subsection available under individual network settings would be useful.
Comment 3 Magnus Therning 2008-03-19 12:13:46 UTC
My testing suggests that xchat-gnome already supports proxy settings since xchat supports it.  What's missing is an interface exposing them:

~/.xchat/xchat.conf :: net_proxy_*

There is another proxy-related thing that needs some attention, preferably urgently.  I raised #523350 for that.
Comment 4 Ritesh Khadgaray ( irc:ritz) 2009-11-20 19:04:13 UTC
*** Bug 596046 has been marked as a duplicate of this bug. ***
Comment 5 Felipe Contreras (banned) 2010-06-08 21:48:46 UTC
Since this bugzilla has no voting support:
+1
Comment 6 Felipe Contreras (banned) 2010-12-01 18:12:10 UTC
I implemented this some time ago.

http://sourceforge.net/tracker/index.php?func=detail&aid=3017821&group_id=239&atid=100239#
Comment 7 Tony Browning 2011-11-01 20:33:39 UTC
My ip address has >changed from Windstream> to this VirginMobile MiFi2200 26C Secure 192.168.1.1, 192.168.1.2, on up etc. I use Fedora 16 Beta(32bit)operating system and xchat-gnome 0.26.1fc16(32bit) keeps searching/closing sockets and reading off this, etc:

Looking up irc.freenode.net..
Connecting to chat.freenode.net (94.125.182.252) port 7070..
 * Subject: /C=US/ST=UT/L=Salt Lake City/O=The USERTRUST Network/OU=http://www.usertrust.com/CN=UTN-USERFirst-Hardware
 * Issuer: /C=US/ST=UT/L=Salt Lake City/O=The USERTRUST Network/OU=http://www.usertrust.com/CN=UTN-USERFirst-Hardware
 * Subject: /C=FR/O=GANDI SAS/CN=Gandi Standard SSL CA
 * Issuer: /C=US/ST=UT/L=Salt Lake City/O=The USERTRUST Network/OU=http://www.usertrust.com/CN=UTN-USERFirst-Hardware
 * Subject: /OU=Domain Control Validated/OU=Gandi Standard Wildcard SSL/CN=*.freenode.net
 * Issuer: /C=FR/O=GANDI SAS/CN=Gandi Standard SSL CA
 * Certification info:
   Subject:
     OU=Domain Control Validated
     OU=Gandi Standard Wildcard SSL
     CN=*.freenode.net
   Issuer:
     C=FR
     O=GANDI SAS
     CN=Gandi Standard SSL CA
   Public key algorithm: rsaEncryption (2048 bits)
   Sign algorithm sha1WithRSAEncryption
   Valid since Jan 14 00:00:00 2011 GMT to Jan 14 23:59:59 2012 GMT
 * Cipher info:
   Version: TLSv1/SSLv3, cipher DHE-RSA-AES256-SHA (256 bits)
 Connected. Now logging in..
 *** Looking up your hostname...
 *** Checking Ident
 *** Found your hostname
 *** No Ident response
 PASS :Not enough parameters
 *** Notice -- You need to identify via SASL to use this server
 Closing Link: 66-87-2-207.pools.spcsdns.net (SASL access only)
 Disconnected (Remote host closed socket).
 Cycling to next server in FreeNode...
 Disconnected ().
 Looking up #fedora..
 Unknown host. Maybe you misspelled it?
 Cycling to next server in FreeNode...
 Disconnected ().
 Looking up #fedora-social..
 Unknown host. Maybe you misspelled it?
 Cycling to next server in FreeNode...
 Disconnected ().
 Looking up #xchat-gnome on irc.freenode.net ..
 Unknown host. Maybe you misspelled it?
 Cycling to next server in FreeNode...
 Disconnected ().
Comment 8 André Klapper 2019-02-23 02:49:12 UTC
xchat-gnome is not under active development anymore.
Its codebase has been archived:
https://gitlab.gnome.org/Archive/xchat-gnome/commits/master

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect
reality. Please feel free to reopen this ticket (or rather reactivate the project
to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the
responsibility for active development again.
You may want to switch to Hexchat (or another IRC client that suits you).