Opened 4 years ago

Closed 13 months ago

#17465 closed defect (wontfix)

Unable to connect to bip IRC proxy

Reported by: lunar Owned by:
Priority: Medium Milestone:
Component: Archived/Tor Messenger Version:
Severity: Normal Keywords:
Cc: tor@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


I am unable to connect to my IRC proxy using Tor Messenger. bip is able to use a single proxy server for multiple networks. The network selection is done at login time using the network password.

I'm not sure what's not working with Tor Messenger. The connection phase never completes. I see a new window with the following message:

The following message received from b.i.p was not encrypted: You should type /QUOTE PASS your_username:your_password:your_connection_name

Is Tor Messenger properly sending passwords for IRC?

(This works just fine with Pidgin.)

Child Tickets

Change History (5)

comment:1 Changed 4 years ago by arlolra

Hmm, do you think you could try in Instantbird nightly to confirm this isn't an upstream issue?

comment:2 Changed 4 years ago by arlolra

aleth says,

it's probably that we try not to send PASS by default and use SASL etc instead
see for an about:config workaround
for znc we detect the bouncer and send PASS, but nobody has done the equivalent for bip afaik
basically, it's a bouncer-specific issue.

comment:3 Changed 4 years ago by lunar

Cool, it works! It's cumbersome, but it works. I'm now on #tor-dev using Tor Messenger. :)

Last edited 4 years ago by lunar (previous) (diff)

comment:4 Changed 4 years ago by clokep

Cc: tor@… added

We could probably get this to work like it does for ZNC if we had a full protocol dump and either:

  1. a server to test against
  2. someone willing to test our changes

See for what we did with ZNC.

Generally I'd complain about how bouncers break a lot of the IRC spec, but I'll spare you my rant. :)

We could also show this option in the UI by fixing, but I haven't had time to work on this in a long time.

comment:5 Changed 13 months ago by traumschule

Resolution: wontfix
Status: newclosed

<+sukhe> hello. yes, I think it's fine to close the tickets. thanks for doing what we should done earlier :)

Note: See TracTickets for help on using tickets.