Opened at 2009-10-01T11:05:26Z
Closed at 2009-10-02T23:17:02Z
#526 closed defect (duplicate)
Yahoo issues
| Reported by: | anonymous | Owned by: | |
|---|---|---|---|
| Priority: | blocker | Milestone: | |
| Component: | BitlBee | Version: | 1.2.3 |
| Keywords: | Cc: | ||
| IRC client+version: | Client-independent | Operating System: | Public server |
| OS version/distro: |
Description
To make Bitlbee work with Yahoo during this period while Yahoo is upgrading and the supporting libs are not yet updated, add any one of the following lines to /etc/hosts (as root) and bitlbee will connect through china where the servers are not yet upgraded.
You can ping the IP numbers listed below to see the connection.
The host name is the one used by bitlbee and needs to be forced to go to one of the chinese servers.
Using sudo and nano :~sudo nano /etc/hosts
or you can use su and pico or vim
202.43.216.31 scs.msg.yahoo.com 202.43.216.6 scs.msg.yahoo.com 202.43.216.74 scs.msg.yahoo.com
Attachments (0)
Change History (2)
comment:1 Changed at 2009-10-02T21:42:47Z by
comment:2 Changed at 2009-10-02T23:17:02Z by
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Come on people, learn to use a bug tracker.
And for this stuff: I don't know how well the obfuscation in the old auth. mechanism worked but if it's based on a proper irreversible hash (and AFAIK it is) with a challenge there's little abuse one could perform using the alternative server. Even replays won't work anymore since none of the Yahoo! servers will give a useful session using that mechanism anymore.
Ummm, I don't like the idea of sending my Yahoo password through some unknown server in China submitted by an anonymous Internet dude. That just seems spectacularly foolish to me....