[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #9022 [Pluggable transport]: Create an XMPP pluggable transport
#9022: Create an XMPP pluggable transport
---------------------------------+------------------------------------------
Reporter: asn | Owner: feynman
Type: task | Status: accepted
Priority: normal | Milestone:
Component: Pluggable transport | Version:
Keywords: | Parent:
Points: | Actualpoints:
---------------------------------+------------------------------------------
Comment(by arma):
Replying to [comment:8 asn]:
> Replying to [comment:4 rransom]:
> > This pluggable transport will (a) give hostile firewall vendors an
incentive to block all XMPP-like traffic, and (b) give XMPP server
operators an incentive to deploy censorship software to detect and block
`hexchat`.
>
> Yes, these are valid concerns.
> Another issue with this PT, is that the XMPP server (e.g. google) learns
the IP address of our users.
>
> Unfortunately, I don't know how to evaluate the severity of these
concerns, and whether it's a good idea to deploy such a transport to
users.
I don't see a problem here. Predicting the future is hard -- maybe some
XMPP servers will choose to censor, and maybe some won't. Probably some
firewall vendors will offer a 'filter xmpp button' (probably some of them
do already). But whether firewall operators choose to press the button
remains a complex tradeoff.
Wrt the 'xmpp servers censoring their content' question: that means the
hexchat design should consider whether it can achieve its goals with
fewer/no regexpable "headers" in its chat setup.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9022#comment:9>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs