[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-bugs] #3469 [Vidalia]: Anomalous Ports in Exit Policies

#3469: Anomalous Ports in Exit Policies
---------------------+------------------------------------------------------
 Reporter:  atagar   |          Owner:  chiiph
     Type:  defect   |         Status:  new   
 Priority:  major    |      Milestone:        
Component:  Vidalia  |        Version:        
 Keywords:           |         Parent:        
   Points:           |   Actualpoints:        
---------------------+------------------------------------------------------
 Hi, the port selections for Vidalia's exit policies [1] seem to have a few
 anomalies...

 18:18 < atagar> chiiph: in looking around I can't find anything saying
 that port 8300 is used for IM traffic (... or really much of anything)
 18:18 < chiiph> atagar: I assume you are still talking about exit policies
 and the ports it allows, yes?
 18:19 < atagar> yup, I'm writing the exit policies section of a realy
 setup wizard and looking into what vidalia does
 18:19 < chiiph> ok
 18:19 < chiiph> well, I'm not sure why that port is there actually :)
 18:20 < atagar> Weird, 8888 is for HyperVM. I wonder why that's there
 too...
 18:22 < asn> (also, maybe comment saying '703' should be changed to '706'
 to match the code and SILCd's port)
 18:22 < atagar> yup, that threw me off for a while :)
 18:37 < velope> port 8300 - Transport Management Interface
 ...
 18:59 < atagar> chiiph: more issues - 194 and 6679 are sometimes used for
 IRC, 531 is also evidently related to both IRC and AIM, and 7000-7001
 *isn't* used for IRC but is a default port for a bittorrent tracker (Vuze)
 18:59 < atagar> that last one seems very bad
 19:00 < atagar> I'll go ahead and file a ticket for this
 19:00 < chiiph> ok, thanks
 19:01 < Riastradh> 7000 is sometimes used for IRC.
 19:01 < Riastradh> oftc uses 6697 for TLSifid IRC.
 19:03 < atagar> Hmm, yup, spotting some mentions of irc on 7000. On the
 other hand including a torrent default's bad for exits due to dmca
 takedowns. Not sure which way we'd like to go on that one...

 Descriptions of common port uses can be found at:
 https://secure.wikimedia.org/wikipedia/en/wiki/List_of_TCP_and_UDP_port_numbers

 Also, the IM option is missing quite a few protocols that are prevalent
 elsewhere in the world. I'd propose that we adopt the following for this
 option...
 706 (SILC)
 1863 (MSN)
 5050 (Yahoo)
 5190 (ICQ, AIM)
 5222 (Jabber)
 5223 (Jabber over SSL)
 1677 (GroupWise)
 8074 (Gadu-Gadu)
 8000-8001 (Tencent QQ)
 1533 (Sametime)
 2102-2104 (Zephyr)

 This includes all of the TCP based protocols supported by Pidgin. If any
 of them are bad news then I'd love to know (I'm writing a similar setup
 wizard for relay setup so looking for sane defaults).

 Port 531 is listed as being related to both AIM and IRC so I'm not sure
 what we'd like to do with that one. In my case I'll probably join the
 IM/IRC options (I'm not sure why they were split...).

 Cheers! -Damian

 [1]
 https://gitweb.torproject.org/vidalia.git/blob?f=src/vidalia/config/ServerPage.cpp#l55

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3469>
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