If the other is doing this as well (Zero i2p SAM hops), this would allow to have direct contacts with retroshare as now it is. You then can choose, if you want to use direct IP connections to the rendevous point of i2p-SAM or to use 1,2,3 hops to be covered with your IP. Maybe it is useful, to have a SAM implementation in retroshare as a general base. This means: it is like freezing a see, one point freezes and then all ice stars will hop to the nearby water.Ī) an anonymous chat system will come some day for the development in i2p so or so andī) that retroshare is very well, if there is an option to hide the IP adresses of your destination (not neighbour), you send traffic to. Then they have all your friends by method a and b. This must not be a problem, if you have trusted friends.īut there might be the case, that you get in the situation to explain your heavy traffic. Retroshare has (in general) the disadvantage, that you reveal your social network,Ī) by the collected pqi certificates on your the hard discĬ) by heavy traffic, you need to explain (e.g. Furthermore Tor cannot handle massive file transfer, which is retroshare/i2p too. the encryption is more along the line and more secure (second channel key transfer) than end to end encryption, and in Tor you have at the rendevouspoint as well an unencrypted handshake (!). I think the i2p network is the better oneĪnd there was also the conclusion, that retroshare over i2p would cover most needsĮ.g. If you do not want to do this, the torirc-nostem.py script doesn't uses Stem, but it's bigger and uglier.Hi there was a long and good talk with a chat developer, who wants to code a messenger to chat anonymously, the Tor system should be considered for that plans. This is more clean but it requires you to install the Stem library and configure the TOR control port. Latest tor-irc version uses the Stem python library to connect and control TOR, and now it makes uses of the system TOR daemon instead of spawning it's own TOR process. This information can be the difference between life and death for some people, so it's a useful problem to tackle IMHO. Network analysis is a hard problem and there are hundreds of side-channels that can be used to determine if a user is connected or not. The server doesn't accurately report the number of clients in the chatroom, it only erases a nick approximately a day after it disconnects (this delay is also random).Every message is padded to minimum_message_len (currently 256 bytes).The client periodically sends random data at random intervals.However, the server knows when a client is connected.Thanks to TOR, nobody, the server or the clients, known the IP address of nobody else.This still is experimental software so no strong network-analysis-proof must be assumed. Torchat: Nice alternative but only P2P, latest versions started to creep with unsafe functionality like emoticons, etc. I do believe they also don't protect against network analysis. Silc: They wrote their own crypto, that's a big mistake. Some plugins like OTR fix some shortcomings, but network analysis is also trivial. MSN/Gtalk/Pidgin: Horrible choices, huge codebases, hundreds of libraries riddled with bugs, vulnerable to exploits, central server sees all your (often plaintext) messages, etc. Also Network analysis is trivial with this protocol. Anyway this is vulnerable to exploits as IRC servers and clients tend to be huge pieces of C code. This is the best alternative, but only if you don't use any public server. Here are alternative software and why I do not like it: Also, the current version of torirc doesn't have his own cryptography routines and uses TOR for it, but this may change in the future. TOR: big ugly chunk of C code that I do not trust entirely, but at this time is the only software that provides the functionality that I need, that is, hidden services and onion routing. Also TOR has Stem, a very nice python-controller lib. Also Python usually comes installed in most Linux distros. Second choice would have been Java, but the JRE is too big and cumbersome. Python: I selected python because it's what I know, and the interpreter is relatively small.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |