[tor-dev] BridgeDB's email server rewrite; NEED CODE REVIEW
Hi everyone! If someone who is comfortable with Twisted Python and SMTP could look over my rewrite of BridgeDB's email servers, that would be great! The servers currently online (they are mostly down, and they keep falling over) had so many bugs that I spent a week and a half trying to stabilise them. Then I spent a mere day and a half rewriting them completely, fixing the following bugs: #5463 #7547 #7550 #8241 #11475 #11753, among others. The relevant branch is my `fix/5463-7547-7550-8241-11475-11753-email-rewrite` branch, [0] and most of the new code can be found in the `lib/bridgedb/email` tree. [1] The relevant ticket for providing feedback would be #5463, where most of the discussion is happening. [2] Since I've already waited about a week for review, and the servers are currently broken and people are complaining at me a lot, I'm giving y'all 48 hours to speak up, else forever hold your pisces. Thanks in advance for reviewing! :) [0]: https://gitweb.torproject.org/user/isis/bridgedb.git/shortlog/refs/heads/fix/5463-7547-7550-8241-11475-11753-email-rewrite [1]: https://gitweb.torproject.org/user/isis/bridgedb.git/tree/refs/heads/fix/5463-7547-7550-8241-11475-11753-email-rewrite:/lib/bridgedb/email [2]: https://trac.torproject.org/projects/tor/ticket/5463 -- ♥Ⓐ isis agora lovecruft _ GPG: 4096R/A3ADB67A2CDB8B35 Current Keys: https://blog.patternsinthevoid.net/isis.txt signature.asc Description: Digital signature ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
[tor-dev] Installing obfsproxy from wheezy-backports
Hello there, tl;dr obfsproxy from wheezy-backports raises exception about not finding Twisted although Twisted-core is installed. I want to install obfsproxy from wheezy-backports on a wheezy machine. The package currently in wheezy-backports [1] depends on : python (= 2.7), python ( 2.8), python-pkg-resources, python-crypto, python-twisted-core (= 13.2) After installation i get: $ obfsproxy Traceback (most recent call last): File /usr/bin/obfsproxy, line 5, in module from pkg_resources import load_entry_point File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2707, in module working_set.require(__requires__) File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 686, in require needed = self.resolve(parse_requirements(requirements)) File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 584, in resolve raise DistributionNotFound(req) pkg_resources.DistributionNotFound: Twisted obfsproxy explicitly requires twisted: $ cat /usr/lib/python2.7/dist-packages/obfsproxy-0.2.7.egg-info/requires.txt PyCrypto Twisted argparse pyptlib = 0.0.5 pyyaml But in /usr/lib/python2.7/dist-packages/ there is only: twisted Twisted_Core-13.2.0.egg-info Meaning obfsproxy doesn't seem to find Twisted, cause there is no Twisted*.egg-info in dist-packages/ directory. Interestingly obfsproxy wheezy package from deb.torproject.org [2] depends on : python (= 2.7), python ( 2.8), python-pkg-resources, python-crypto, python-twisted, python-pyptlib (= 0.0.4), python-yaml (The same goes for obfsproxy in debian testing.) Notice it's 'python-twisted' and not 'python-twisted-core'. So the package from deb.torproject ends up installing a Twisted*.egg-info in /dist-packages and obfsproxy does not complain. So i'm wondering, is this a bug? Should i file a debian bug for the debian package in wheezy-backports? Does obfsproxy need all of twisted dependencies or 'python-twisted-core' suffices? If the latter how may we fix the original exception? Cheers, Alex [1]: https://packages.debian.org/wheezy-backports/obfsproxy [2]: https://deb.torproject.org/torproject.org/dists/wheezy/main/binary-amd64/Packages signature.asc Description: OpenPGP digital signature ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Re: [tor-dev] GSoC: Ahmia.fi - Search Engine for Hidden Services
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Some updates. Ahmia have now fresh new YaCy back-end installed. Unfortunately, I messed up with Solr and eventually we might have to destroy and re-crawl everything again. At the moment, it at least works. Then some good news. I created a milestone to github. There are all the main features and I try to develop them as fast as I can :) https://github.com/juhanurmi/ahmia/issues?milestone=1page=1state=open Currently, I have worked some code to gather popularity stats and new domains from tor2web nodes and saving them to ahmia.fi. Furthermore, I have built a tool that checks backlinks from the public WWW! This data is useful for the popularity measurements. I am already pushing code to github :) Cheers, Juha -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTcRgHAAoJELGTs54GL8vA2jAH/j2aIV158GSpS+udWM62PfsM 3RxTkzfnfxRT5JPC/BtVNqzDCwnyePskK3FVR6etd+rA9XD55He6Kb9EAFypfkK4 QI/2/IVViWOZzL/S55bz97/DbBPPCpIoesd20cUNC08qK57FnZZOKrQFCVtyL11i MskET/TMIZLFgXjLlCoGCsGvCt386OjbN1A0aAJkEwvKf9EfWEZdDED12nj4jaMB s6+dKr8+4jJt8hBKsrPSw1Kcb7UNBBzFGUL/N75Rl4fVToE9YJyLtNHhogy7z2JH d9JFuIcoSl/ZK/Ly1W/91DcJgZQwVU4fUedQ/aWocPO/HSxaUXsgIir88BoX89M= =2TIk -END PGP SIGNATURE- ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
[tor-dev] Missing days in Bridge users by transport
Do you know what is the cause of the missing data between April 14 and April 22 in this graph? I'd like to be able to account for it when I present the graph. https://metrics.torproject.org/users.html?graph=userstats-bridge-transporttransport=meek#userstats-bridge-transport I don't suppose it is a problem with the bridge, because other transports show the same gap. https://metrics.torproject.org/users.html?graph=userstats-bridge-transporttransport=obfs3#userstats-bridge-transport https://metrics.torproject.org/users.html?graph=userstats-bridge-transporttransport=fte#userstats-bridge-transport David Fifield ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Re: [tor-dev] Introduction Points and their rotation periods (was Re: Hidden Service Scaling)
On Sun, May 11, 2014 at 11:33 AM, Michael Rogers mich...@briarproject.org wrote: However, that might require all three nodes in the circuit to be picked from the high-uptime pool. Can't be certain but I think Phantom picks the entire circuit and then camps on it till it breaks somewhere. Their paper might give other views/ideas on such things. Another thought, the benefits of 'longer' camping on an entry seem sound to me (you're either safe or not straight away, vs likely not safe sometime in the future or even straight away.) Does the EG camp time come down to estimating the number of EG's in the environment that are unsafe? Also, if you camp on a whole circuit your usage is more timeable by a PA who might catch your tail. So perhaps making the circuit be an anchored flagellum, farther from the EG, more flipping about. Sometimes with just a shimmy in the middle. ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Re: [tor-dev] Finding the catch probability
Hi, Everything you need to know about running experiments on Shadow: https://github.com/shadow/shadow/wiki (Including installation) ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Re: [tor-dev] Finding the catch probability
Hi, I have installed the shadow(v 1.9.2) and ran it also. Then I perform the following process: I will first use any of the four examples included in the scallion directory. 2. In shadow.config.xml file, numbers of clients, guard, middle, exit and webservers are configured. 3. Lets suppose that I added certain number of guard or exit nodes with high bandwidth in this shadow.config.xml file and run the simulation. The clients will try to download a file from the webserver by selecting three nodes, according to path selection algorithm, among these all nodes including mine inserted nodes also. 4. Now I want to observe the probability of selection of my inserted nodes as entry or exit nodes by the clients* (catch probability)*. 5. Again I will change the number of nodes to be inserted and run the simulation and find the catch probability. After running the simulation, a log file will be created, scallion.log. So using this log file, how to find the catch probability by using the analyze.py script? Thanks, On Tue, May 13, 2014 at 12:50 PM, Sukhbir Singh sukhbir...@gmail.comwrote: Hi, Everything you need to know about running experiments on Shadow: https://github.com/shadow/shadow/wiki (Including installation) ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev -- Saurav Dahal, Wireless communication and Networking lab, Dept. of Computer Engineering, Chosun University, 309 Pilmun-daero, Dong-gu Gwangju, 501-759 S.KOREA ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
