February 2012 Progress Report
Our progress report for February 2012 is now available. It hightlights recent work with deep packet inspection and censorship circumvention in Iran and Kazakhstan. Also progress on a new tor status site based on new protocols, and general outreach and travels.
We implemented a new format this month to better reflect everything going on within Tor.
Available as a pdf with full color graphs, https://archive.torproject.org/monthly-report-archive/2012-February-Mon…
or as a plain text file for portability and readability, https://archive.torproject.org/monthly-report-archive/2012-February-Mon…
Try changing port 443 to something extremely high and unused like 8922. After doing so restart tor and verify there are no errors in the logs.
I have a great idea. Please create a new project together with EFF that would find any possible data leaks from the computer. Most people don't know or cannot understand the risks of using programs, opening files, reading emails, etc. or simply there could always be problems with the configurations. So both the beginners and advanced users could benefit from this project.
This could be used for checking Office files, PDF files, torrent files, emails (with HTML), etc. (for any potentially dangerous type) where data leaks or unwanted internet connections could happen.
There will be test files for each type which would directly connect to EFF and therefore the user could see the test results from a webpage. Or a safer way, localhost-linked files alongside a program to catch connections going to localhost [Will this work for "2." below? Maybe there should be options for both of them a) eff website b) localhost]
Here are the purposes:
1- Check whether an internet connection is happening or not.
2- If there's a connection, show the user's connecting IP. (To check if the anonymizer is working correctly: VPN, Tor, etc.)
3- Check every possible data leaks. What kind of identifiable information goes to Internet.
4- (If possible) Check if malicious scripts can be executed (for example office & pdf files) which can either send data immediately or change settings in the OS or applications for long term data leaks.
5- Maybe not just applications, but also the OS could be tested? (a further idea, not essential)
I think this is a good starting point. All known attack types could be implemented and also updated after new attacks are discovered.
Inspiration from: http://checkmytorrentip.com/