adding an SSL/SSH option for freenet nodes

Bad news from Belgium show that users of tools like Freenet
 need to hide from packet sniffing of their ISP, even in
 western countries.
It is high time for steganography (hiding/tunneling) options
 for freenet nodes that could be hurt in the near future.
In most western countries laws against encryption are diminishing.
So let's use common ways of encryption like SSL or SSH so that
 no one can know you are using them for freenet instead of 
 http/telnet/ftp/Xforwarding/pop/smtp or whatever SSL or SSH
 are usually used for nowadays. (especially openSSH and openSSL)
IPsec should become a standard but is not much used now, AFAIK.

The idea is to associate to each node address 3 fields that describe
 the encryption(s) used by this node to hide: none, SSH and/or SSL,
 port numbers of sshd/ssld and public key.
Then each time we send a request to this host we know what secure socket
 to use instead of the standard ones we use now.
Nodes that choose this option should make sure ssld/sshd are running
 each time freenet_server is started.

I think a first draft of the freenetSSL option could be implemented in the
next
release of freenet. Especially if you help me do so ...

Thanks for your comments, and your code :)

freessl at gmx.fr

-- 
Sent through GMX FreeMail - http://www.gmx.net


_______________________________________________
Devl mailing list
Devl at freenetproject.org
http://www.uprizer.com/mailman/listinfo/devl

Reply via email to