Opened 14 years ago

Last modified 6 years ago

#469 assigned Enhancement

SSH connecttion -> SOCKS aware

Reported by: XyonN Owned by: timothy
Component: Colloquy (Mac) Version: Local Build
Severity: Normal Keywords: SSH SOCKS PROXY


Would it be possible to for a next release to build in SSH support (and with it, terminal bash)? That way I could connect thru SSH and open my existing screen there.

Change History (9)

comment:1 Changed 14 years ago by timothy

  • Status changed from new to assigned

Do you mean an SSH tunnel? What command do you use to do this manually?

comment:2 Changed 14 years ago by Mark Grimes

  • Keywords SOCKS added
  • Summary changed from SSH connecttion to SSH connecttion -> SOCKS aware

This would be more practical if Colloquy was SOCKS-capable. Then you could use Network.prefPane SOCKS Proxy to point at localhost:lport with "ssh -D <lport> user@remote_host_w_ssh [-p ssh_on_diff_port?] -CNvv"

I use irssi in this situation as I don't want to poke another hole with dircproxy and more tunnels, whereas web browsing can be accomplished using this same application proxy tunnel as above, and anything else pointing at the socks port.

comment:3 Changed 14 years ago by ShadowBottle

Here here. SOCKS proxy would be excellent. This seems to be a basic necessity and I'm shocked it's not available.
Deal breaker for me... back to BitchX and X-Chat Aqua.

comment:5 in reply to: ↑ 4 Changed 13 years ago by Shadowbottle

Replying to akempgen:

check out "How do I make Colloquy use an SSH tunnel?" in the FAQs

This isn't really a great fix or workaround, especially for those of us who already have a dynamic tunnel (or socks proxy setup) and an ssh agent. If you look at xchat aqua you merely point the irc server to the already existing tunnel and port. This should be seriously easy to implement. An example of a dynamic tunnel or SOCKS proxy:
ssh -N -p 22 -c blowfish -D 8008 username@…

Where -D denotes dynamic (meaning that any port request sent through the tunnel goes through regardless of what that port may be), 8008 is the local port its tunneling from the local machine to the host. So essentially I would like to be able to configure each server to connect to localhost on port 8008 using SOCKS proxy (which would essentially request all data on usually 6667 to be requested through the tunnel). Just like any other proxy.

Seriously. I'd love to use Colloquy... but it's just too much work when every single other irc client for OS X out there has this option already integrated. Why would I create a tunnel specifically for port 6667 when I already have a dynamic tunnel established as soon as I log into my account in OS X? My ssh agent takes care of all the work and stores all my keys and makes all my connections for me. Colloquy should be able to take advantage of the already established connections instead of requiring me to setup a tunnel just for it.
ramtops at the gmail if further elaboration or collaboration is necessary.

comment:6 Changed 12 years ago by Turias

  • Keywords PROXY added

I love Colloquy and this is the one feature that is preventing me from being able to use it. Is there any chance we can get SOCKS5 proxy support? I know the SSH tunnel works, but it is annoying to have to open up 4 different SSH connections if I want to connect to 4 IRC servers. It would be great if Colloquy worked like Adium and could pick up the system-wide SOCKS5 proxy setting in my internet configuration.

comment:7 Changed 12 years ago by AR

I would greatly appreciate the addition of the feature, it is the only reason I had to buy Linkinus (yes i needed it badly enough to buy an irc client).

Please guys, its a must for many users including myself.

comment:8 Changed 12 years ago by Grackle

This is a blocker for me. I'd love to be able to use colloquy on my laptop, but I can't do it without socks5 support (preferably through the global system settings, see second comment.) Currently looking for a workaround.

comment:9 Changed 6 years ago by IrishMASMS

Six years and more for this request - and no progress? I haz a sad. :(

Still needed - the work around is bogus, and not workable for those who are unable to use SSL tunnel but using OpenVPN for all their access. Using the dynamic tunnel established is the preferred and more established method.

Please advise.

Note: See TracTickets for help on using tickets.