JonDo 00.13.001 - Protect your privacy on the Internet (was Java Anonymous Proxy). (Free)
Each mix carries out cryptographic operations on the message so that the JonDo-encrypted data is only readable after having passed through the proper mixes in the proper order. This ensures that an eavesdropper either only receives unreadable (encrypted) data or can no longer determine the sender. In order for it to work correctly, only one mix in the cascade needs be trusted not to inform the eavesdropper about the method of message mixing. The more users that use the cascade, the harder it is for an observer to distinguish single users.
Data retention resistance - By the distribution on different, independent operator organisations and countries, the JonDonym service is secure against data retention. Even if single operators have to store data, this does not create an \"overall picture\" needed to uncover the identity of users. Thus, JonDonym provides maximum protection against operators and third parties.
Moreover, the system provides so-called forwarding functionality. Users can connect to the service even if it is blocked by their provider. This is often the case in countries that are known for heavy censorship. Unblocked users of the service (Forwarding servers) may voluntarily forward other JonDonauts (Forwarding clients) to the Mix Cascades.
[Stable release; date: 2010-08-31]
New security features
- Less secure services with only one Mix and only one operator (like Dresden) are now separated from the other services. They are only accessible by using a special filter named "Test/experimental services" in order to prevent a connection if a user does not deliberately want it.
- Anonymous HTTP header signature of the internal JonDo HTTP filter is now the same as the new JonDoFox HTTP header signature.
- If a connection from the JonDoFox browser is recognized, the internal HTTP filter of JonDo is deactivated for this connection, because JonDoFox can do the HTTP anonymization much better than JonDo alone.
- Removed global socket listener: JonDo can now only listen on "localhost" and cannot be forced any more to accept connections from outside your own computer (if you really need this feature, use JonDoConsole). This prevents others from misusing your JonDo connections in case you had accidentially allowed global access.
- Check type and ID of each account challenge in order to prevent first mixes from reading the user's balance.
Usability enhancements
- Spanish translation
- Switching, disconnecting and reconnection of services is much faster now and more robust against network problems.
- Updates of infoservice and payment information on startup is much faster now.
- Support for a new type of payment rates: monthly rates that provide the same data volume each month. These rates will be introduced within the next weeks.
Bugfixes
- If anonymous mode is OFF: non-anonymous "direct" proxy can now open arbitrary long URLs, is immediately updated if its settings change and is automatically initialized when JonDo starts.
- Proxy authentication (proxy login with username and password) works again.
- Services that change their certificates are now affected by the auto-blacklist.
- Old/lost cost confirmations are now correctly restored when received from the first mix.
- KDE4 update works again
- External browser in portable mode may now be set on all operating systems and to all local file paths.
- use 127.0.0.1 instead of localhost for default socket listener in order to prevent IPv6 connections to JonDo
- block internal auto-update if Java Web Start is recognized
- raised update intervals for database entries and reduced number of contacted InfoServices in order to draw load from InfoServices and payment instance
- fixed many other small bugs and instabilities...