[Telepathy-commits] [telepathy-gabble/master] add NEWS entry about SOCKS5 bug

[Guillaume Desmottes]

---
 NEWS |   25 +++++++++++++++++++++++++
 1 files changed, 25 insertions(+), 0 deletions(-)

diff --git a/NEWS b/NEWS
index 847d6f4..6179f66 100644
--- a/NEWS
+++ b/NEWS
@@ -1,6 +1,31 @@
 telepathy-gabble 0.7.22 (UNRELEASED)
 ====================================
 
+Fixes:
+
+* Fix SOCKS5 implementation to actually respect XEP-0065.
+  One of the changes would cause interoperability issues with
+  older, buggy, Gabble implementing SOCKS5 (0.7.{18,19,20,21}):
+
+  - A stream tube (muc or private) offers from a new Gabble to an old one will
+    takes 30 extra seconds trying to connect and will then timed out and
+    fallback to IBB.
+
+  - A MUC stream tube offered from an old Gabble to a new one will fail
+    during SOCKS5 negotiation and then fallback to IBB.
+
+  - A private stream tube offered from an old Gabble to a new one will,
+    apparantely, connect properly but the server application (tube offer side)
+    will receive crap data from the tube socket.
+
+  - Same problem with a private D-Bus tube offered by a new Gabble to an
+    old one: the receiver of the tube will receive wrong data.
+
+  These problems only appear when a SOCKS5 connection is possible, so
+  generally when both peers are on the same network. If they are not,
+  SOCKS5 connection will probably be impossible because of NAT's and
+  they'll fallback to IBB as usual.
+
 telepathy-gabble 0.7.21 (2009-02-19)
 ====================================
 
-- 
1.5.6.5