[tor-reports] my report for september

dawuud dawuud at riseup.net
Fri Sep 30 12:53:14 UTC 2016


This status report is for auguest 30th - September 30 inclusive.
Unfortunately I was unable to attend the tor-dev meeting in Seattle. :(


subgraph
--------

- we plan to remove procsnitch as a dependency of roflcoptor
because procsnitch cannot reliably retreive info about unix domain socket
connections and we don't really need it to apply filter policies because
we can tie a policy to a particular listener to do this instead.

https://github.com/subgraph/roflcoptor/issues/56

awaiting code review here
https://github.com/subgraph/roflcoptor/pull/60

bwscanner
---------

- i recently chatted with a code contributor to bwsanner who is interested
in making the partition-attack detector work;
they posted some code that demonstrates the circuit permutation generator
that has the features we want like partitioning and low, memory cpu overhead
for lazily generating 49 million circuit pairs etc.
https://github.com/TheTorProject/bwscanner/issues/23

IPFS Tor integration
--------------------

- I made some fixes to the onion ipfs transport and started to write
unit tests for it when i realized that IPFS has broken their build
system so I'm currently blocked on this issue:

https://github.com/david415/ipfs-onion-transport
https://github.com/ipfs/notes/issues/37#issuecomment-249066032


Tahoe-LAFS Tor integration
--------------------------

Brian Warner posted a summary of our latest Tor integration work
and design discussions:
https://tahoe-lafs.org/pipermail/tahoe-dev/2016-August/009771.html

recently I worked on:

* cleaned up Tor docs
  https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2830

*  Grid Status displays wrong Address of connected storage servers 
  https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2818

  When I was testing the Tor integration in client-mode by connecting
  to the public-grid I noticed the grid status web page displaying the
  wrong address of the connected storage servers.

* tor connection-handler should do SOCKS over arbitrary endpoint 
  https://foolscap.lothar.com/trac/ticket/265

* allow tor socks.port= to use unix-domain sockets 
  https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2813

* `tahoe create-node` should require `--location` and/or `--hostname`, and not autodetect
  https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2773

reviewed code for:

* Brian Warner's pull requests for:
  anonymous client mode
  https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1010
  https://github.com/tahoe-lafs/tahoe-lafs/pull/330
  https://github.com/tahoe-lafs/tahoe-lafs/pull/326/files
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-reports/attachments/20160930/18119960/attachment.sig>


More information about the tor-reports mailing list