> I'm no expert on TCP/IP connections and such, but even if FProxy rejects > all non-localhost connections, can the attacker still find out that > there's something running on port 8080, and then portscan for the node? Port 8080 is a normal port to run a web server on. So running FProxy on port 8080 is not very suspicious. > If so, we absolutely must randomize the fproxy listener port as well as > the node port. Right? This is probably a good idea anyway. _______________________________________________ Freenet-dev mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/mailman/listinfo/freenet-dev
- [Freenet-dev] Gaping hole in FProxy: fix or wait. Mark J. Roberts
- Re: [Freenet-dev] Gaping hole in FProxy: fix or wait. Mark J. Roberts
- Re: [Freenet-dev] Gaping hole in FProxy: fix or w... Scott G. Miller
- Re: [Freenet-dev] Gaping hole in FProxy: fix or w... Brandon
- Re: [Freenet-dev] Gaping hole in FProxy: fix ... Travis Bemann
- Re: [Freenet-dev] Gaping hole in FProxy: fix or wait. Brandon
- Re: [Freenet-dev] Gaping hole in FProxy: fix or w... Mark J. Roberts
- Re: [Freenet-dev] Gaping hole in FProxy: fix ... Brandon
- Re: [Freenet-dev] Gaping hole in FProxy: ... Scott G. Miller
- Re: [Freenet-dev] Gaping hole in FProxy: ... Mark J. Roberts
- Re: [Freenet-dev] Gaping hole in FPr... Brandon
- Re: [Freenet-dev] Gaping hole in... Mark J. Roberts