bugWeeChat - Bugs: bug #28712, Can't connect using arbitrary...

 
 

bug #28712: Can't connect using arbitrary local_hostname

Submitted by:  Sterling X. Winter <sterlingwinter>
Submitted on:  Fri 22 Jan 2010 06:33:59 PM UTC  
 
Category: irc pluginSeverity: 3 - Normal
Item Group: otherStatus: Invalid
Privacy: PublicAssigned to: Sebastien Helleu <flashcode>
Originator Name: Open/Closed: Closed
Release: 0.3.0IRC nick: 

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

(Jump to the original submission Jump to the original submission)

Wed 07 Jul 2010 01:54:20 PM UTC, comment #7:

Then use "username" field in server to change name before "@" in hostname.
Option "local_hostname" is something different, it is used for IP connection to server.

Sebastien Helleu <flashcode>
Project AdministratorIn charge of this item.
Tue 29 Jun 2010 05:55:29 AM UTC, comment #6:

If this is just misuse of the option, could you please provide a sample of how? I took my whois info from logging in without setting the local_host, then changed only the name prior to the @ to test (~test@c-xx-xxx-xxx-xxx.hsd1.fl.comcast.net) and it did not work. How can we have it not display my own computer's ident (if nothing else, for privacy concerns, I don't always want my login name to be known to the world).

Shawn <shawnr13>
Tue 29 Jun 2010 05:53:30 AM UTC, comment #5:

If this is just misuse of the option, could you please provide a sample of how? I took my whois info from logging in without setting the local_host, then changed only the name prior to the @ to test (~test@c-xx-xxx-xxx-xxx.hsd1.fl.comcast.net) and it did not work. How can we have it not display my own computer's ident (if nothing else, for privacy concerns, I don't always want my login name to be known to the world).

Shawn <shawnr13>
Sun 21 Feb 2010 08:12:22 AM UTC, comment #4:

I just looked at code, this option (local_hostname) is not used if you're using a proxy. That's why there is no error.

And if you don't use proxy, this option must contain a valid address, WeeChat tries to resolve it. If you set "test", this can not work.

For me, there's no bug, it's a problem using option.

Sebastien Helleu <flashcode>
Project AdministratorIn charge of this item.
Sun 21 Feb 2010 01:28:51 AM UTC, comment #3:

This is still marked "Need Info." Do you need me to provide anything else?

Sterling X. Winter <sterlingwinter>
Sat 30 Jan 2010 11:55:04 AM UTC, comment #2:

Sorry, it doesn't appear to be a regression after all. I thought that I had it working before with an arbitrary hostname in 0.2.6.x. I just installed 0.2.6.3 again to check, but you're right, it failed to connect after I performed:

/set freenode.server hostname = "test"
/connect freenode

and I get the same error message that I got with 0.3.1. And also like 0.3.1, I am able to connect if I route the connection though a proxy.

Sterling X. Winter <sterlingwinter>
Fri 29 Jan 2010 03:50:41 PM UTC, comment #1:

I just tried with old version 0.2.6, behaviour was the same.
So why are you talking about "regression", do you know an old version where behaviour was different?
I'm not saying there's not bug, just wanted to know if it was working with anohter version, before investigating on problem.

Sebastien Helleu <flashcode>
Project AdministratorIn charge of this item.
Fri 22 Jan 2010 06:33:59 PM UTC, original submission:

WeeChat 0.3.0 introduces a behavioral regression with custom local hostname settings. To reproduce with version 0.3.0 using an all-default configuration:

1. Make sure you can connect using only default settings:

/connect freenode
(wait for successful connection)
/close

2. Set local_hostname to "test" and try to reconnect:

/set irc.server.freenode.local_hostname test
/connect freenode

WeeChat will fail to connect, giving the following messages:

freenode | irc: connecting to server chat.freenode.net/6667...
freenode =!= | irc: unable to set local hostname/IP
freenode | irc: reconnecting to server in 30 seconds

3. Configure the freenode server to use a proxy (in this example, a locally-running instance of Tor) and reconnect again:

/close
/proxy add tor socks5 127.0.0.1 9050
/set irc.server.freenode.proxy tor
/connect freenode

WeeChat connects successfully using a proxy. (After connection, if the server recognizes your proxy as a Tor node it will disconnect you as per freenode policy, but that isn't relevant to this bug.)

I'm not sure why an arbitrary local_hostname string should prevent connections when a proxy isn't used. WeeChat should not in any circumstance attempt to resolve the string to an actual host. The RFCs covering the IRC protocol do not require a client-to-server hostname string to be valid or of any particular use to the server -- the string is only specified for use in server-to-server communications and is only guaranteed to be valid for that use.

Sterling X. Winter <sterlingwinter>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by shawnr13 (Posted a comment)
  • -unavailable- added by flashcode (Posted a comment)
  • -unavailable- added by sterlingwinter (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 5 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Sat 07 Aug 2010 09:54:02 AM UTCflashcodeOpen/ClosedOpen=>Closed
    Sun 21 Feb 2010 08:12:22 AM UTCflashcodeStatusNeed Info=>Invalid
    Fri 29 Jan 2010 03:50:41 PM UTCflashcodeItem GroupNone=>other
      StatusNone=>Need Info
      Assigned toNone=>flashcode

    Back to the top


    Powered by Savane 3.1-cleanup1