Make the incoming port changeable

Bug #480233 reported by Emilien Klein
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
BaShare
Confirmed
Wishlist
Guiodic (Guido Iodice)

Bug Description

Originally reported by sziszi in Bug #479692, as question 2:

Bug or Feature?
If I setted the outgoing port to x and the incoming port automatically setted to x+1. If someone know my opened outgoing port(I don't have got any UPnP capable router(Crappy chinese junk) and I can't open UPnP port) the Someone can break into my computer, right? Make the incoming port changeable please.

First answer by Guido:
About security issue, it does no matter. Port and "port+1" are both opened, so if a cracker wants to crack you he can do it in port. The problem isn't to know a opened port, a 5 years old child can know this...
About all webserver use tcp port number 80 :)
To crack someone you need to use a vulnerability in the server program.

Second answer by Guido:
p.s. if you have not opened port on router, you have not opened port+1 too.

Third answer by Guido:
2) security: it is not a security hole. But as feature, I can introduce it in a next release

Tags: port request
Changed in bashare:
importance: Undecided → Wishlist
status: New → Confirmed
assignee: nobody → Guiodic (Guido Iodice) (guido-iodice)
Changed in bashare:
milestone: none → 0.5.1
tags: added: port
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.