[freenet-support] A beginner's analysis of Freenet's method of communication
From my understanding, there is a fundamental flaw in p2p technologies like Freenet for those that want to deploy in highly-censored countries. That is, it's too obvious. The censor doesn't have to know what's being transmitted, only that /something/ is that's outside of their control. All they have to do is disallow the ports on which the technology runs. Torrenters can at least get around this by changing the port they're using; Freenet has no such option. From my understanding of internet communication protocols, the use of udp is too obvious; it stands out like a sore thumb. Why not tunnel the connection over tcp? Wouldn't that prevent potential censors from differentiating it from the rest of transmitted data? As well, wouldn't it solve the closed ports issue? I'm sure some of my conclusions are based off of an incomplete understanding of the technologies involved, but I couldn't think of a better way to find out than to put my ideas out there. ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] A beginner's analysis of Freenet's method of communication
On Sun, Oct 24, 2010 at 9:38 PM, Daxter xovat...@gmail.com wrote: From my understanding, there is a fundamental flaw in p2p technologies like Freenet for those that want to deploy in highly-censored countries. That is, it's too obvious. The censor doesn't have to know what's being transmitted, only that /something/ is that's outside of their control. All they have to do is disallow the ports on which the technology runs. Torrenters can at least get around this by changing the port they're using; Freenet has no such option. Every node chooses random ports for opennet and darknet during the installation. You can change them if you want. From my understanding of internet communication protocols, the use of udp is too obvious; it stands out like a sore thumb. Why not tunnel the connection over tcp? Wouldn't that prevent potential censors from differentiating it from the rest of transmitted data? As well, wouldn't it solve the closed ports issue? No, it's not that easy. You clearly don't know what you're talking about. ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] A beginner's analysis of Freenet's method of communication
On Oct 24, 2010, at 3:22 PM, Romain Dalmaso wrote: On Sun, Oct 24, 2010 at 9:38 PM, Daxter wrote: From my understanding, there is a fundamental flaw in p2p technologies like Freenet for those that want to deploy in highly-censored countries. That is, it's too obvious. The censor doesn't have to know what's being transmitted, only that /something/ is that's outside of their control. All they have to do is disallow the ports on which the technology runs. Torrenters can at least get around this by changing the port they're using; Freenet has no such option. Every node chooses random ports for opennet and darknet during the installation. You can change them if you want. I hadn't understood that. Thank you for explaining. How would someone change those ports? From my understanding of internet communication protocols, the use of udp is too obvious; it stands out like a sore thumb. Why not tunnel the connection over tcp? Wouldn't that prevent potential censors from differentiating it from the rest of transmitted data? As well, wouldn't it solve the closed ports issue? No, it's not that easy. You clearly don't know what you're talking about. No, I don't I had already said so in my post, but thank you for stating the obvious. I'm not here because I know everything and I want to bestow divine wisdom; I'm here because I want to learn. Would you care to explain what I don't understand, or at least point me towards topical resources? In particular I'm asking: why not tunnel connections in a manner similar to VPN? ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] A beginner's analysis of Freenet's method of communication
On Sun, 24 Oct 2010 16:03:59 -0500, Daxter wrote: In particular I'm asking: why not tunnel connections in a manner similar to VPN? You can, with darknet ... form your own ssh tunnels with friends, etc. ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] A beginner's analysis of Freenet's method of communication
2010/10/24 Daxter xovat...@gmail.com: From my understanding, there is a fundamental flaw in p2p technologies like Freenet for those that want to deploy in highly-censored countries. That is, it's too obvious. The censor doesn't have to know what's being transmitted, only that /something/ is that's outside of their control. All they have to do is disallow the ports on which the technology runs. Torrenters can at least get around this by changing the port they're using; Freenet has no such option. Hmm, can't find that option either. but there are node.opennet.listenPort and node.listenPort (for Darknet) options in freenet.ini From my understanding of internet communication protocols, the use of udp is too obvious; it stands out like a sore thumb. Why not tunnel the connection over tcp? Wouldn't that prevent potential censors from differentiating it from the rest of transmitted data? As well, wouldn't it solve the closed ports issue? Transport plugins are planned for some remote future release (after 1.0). This will enable use of TCP, embedding Freenet data into HTTP requests, or other protocols, I gather. ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] A beginner's analysis of Freenet's method of communication
On 25.10.2010 5:28, Dennis Nezic wrote: On Sun, 24 Oct 2010 16:03:59 -0500, Daxter wrote: In particular I'm asking: why not tunnel connections in a manner similar to VPN? You can, with darknet ... form your own ssh tunnels with friends, etc. Not if the port is closed. SSH tunnel is created to map the external open port to a port on localhost. If the port is not open you still can't connect. - Volodya -- http://freedom.libsyn.com/ Echo of Freedom, Radical Podcast None of us are free until all of us are free.~ Mihail Bakunin ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
