https://bugs.kde.org/show_bug.cgi?id=356201
Bug ID: 356201
Summary: Send file operation fails due to Socks5 proxy protocol
error
Product: kopete
Version: 1.7.2
Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: NOR
Component: Jabber Plugin
Assignee: kopete-bugs-n...@kde.org
Reporter: kuch...@gmail.com
After a few debug runs, wireshark trace sessions and kopete recompilations
problem is found.
Issue is visible when Kopete sends files to other clients (confirmed with
Pidgin).
According to Socks5 description on wiki
(https://en.wikipedia.org/wiki/SOCKS#SOCKS5) client should send greeting
message (socks version, supported authentication methods) and server side
sockets should respond to that with one selected method or error if non of is
supported.
Problem with kopete (at least without libjingle support) is that no matter
Kopete acts as a client or as a server greeting message always show up in
communication from kopete side.
This in case Kopete is server side client like Pidgin after sending greeting
messages expects to get two bytes (socks_version, selected_auth_method | 0xff)
but it gets a kopete greeting message and this is interpreted as server
selected gssapi authentication method (which even was not on cliend support
list).
Reproducible: Always
Steps to Reproduce:
1. Send a file to other client (checked with Pidgin)
2. Other side accepts
Actual Results:
Send operation fails immediately from Kopete side (in Pidgin console Socks5
session issue can be found).
Expected Results:
File is actually transfered
Quick and dirty modification of
protocols/jabber/libiris/src/irisnet/noncore/cutestuff/socks.cpp to prevent
sending greeting message (in sock_connected) when SocksClient is on Server
socket end helps and file transfer in both directions (Kopete <-> Pidgin) work.
--
You are receiving this mail because:
You are watching all bug changes.
