[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Weechat-dev] [bug #28712] Can't connect using arbitrary local_hostname

From: Sterling X. Winter
Subject: [Weechat-dev] [bug #28712] Can't connect using arbitrary local_hostname
Date: Fri, 22 Jan 2010 18:34:00 +0000
User-agent: Mozilla/5.0 (compatible; Konqueror/4.3) KHTML/4.3.4 (like Gecko)


                 Summary: Can't connect using arbitrary local_hostname
                 Project: WeeChat
            Submitted by: sterlingwinter
            Submitted on: Fri 22 Jan 2010 12:33:59 PM CST
                Category: irc plugin
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 0.3.0
                IRC nick: 



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)

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:

    /proxy add tor socks5 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


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]