Loading HACKING +1 −1 Original line number Diff line number Diff line Loading @@ -8,7 +8,7 @@ Read the README file first, so you can get familiar with the basics. 1. The pieces. 1.1. Routers. Onion routers, as far as the 'or' program is concerned, 1.1. Routers. Onion routers, as far as the 'tor' program is concerned, are a bunch of data items that are loaded into the router_array when the program starts. After it's loaded, the router information is never changed. When a new OR connection is started (see below), the relevant Loading TODO +38 −1 Original line number Diff line number Diff line [First four are all equally first. Others follow in order of priority.] Patch well-known proxies to make them OR compliant Data stream anonymizing, HTTP/FTP (Privoxy, Squid), SMTP, etc. Packet Redirector, a la FreeBSD (DNS, authenticated connections, etc.) Deploy and manage open source development site. Manage and maintain code, write documentation, design and write unit tests, handle patch submissions, make the autoconf work, etc Deploy a widespread network: manage deployment. Maintain and distribute directory/network state information etc. Keep operators and users happy. Test OR network for reliability and performance, with and without mechanisms for throttling, congestion control, padding, load balancing if applicable, etc. Use httperf and webload to get some performance stats Modify code as dictated by testing. Develop rendezvous points Implement reply onions Develop location protected servers idea Enhance router twins to do load balancing as well as DoS prevention Develop and deploy automated reputation management, directory servers, and directory/network state monitoring. --- debian / red hat spec file handle starting things as a system daemon transition addr to sin_addr Obvious things I'd like to do that won't break anything: * Abstract out crypto calls, with the eventual goal of moving * Abstract out crypto calls (done), with the eventual goal of moving from openssl to something with a more flexible license. * Test suite. We need one. Loading src/or/Makefile.am +3 −3 Original line number Diff line number Diff line Loading @@ -3,11 +3,11 @@ TESTS = test_config noinst_PROGRAMS = test_config bin_PROGRAMS = tor bin_PROGRAMS = or tor_LDADD = -L../common -lor or_LDADD = -L../common -lor tor_SOURCES = buffers.c cell.c circuit.c command.c connection.c \ or_SOURCES = buffers.c cell.c circuit.c command.c connection.c \ connection_exit.c connection_ap.c connection_op.c connection_or.c config.c \ main.c onion.c routers.c Loading Loading
HACKING +1 −1 Original line number Diff line number Diff line Loading @@ -8,7 +8,7 @@ Read the README file first, so you can get familiar with the basics. 1. The pieces. 1.1. Routers. Onion routers, as far as the 'or' program is concerned, 1.1. Routers. Onion routers, as far as the 'tor' program is concerned, are a bunch of data items that are loaded into the router_array when the program starts. After it's loaded, the router information is never changed. When a new OR connection is started (see below), the relevant Loading
TODO +38 −1 Original line number Diff line number Diff line [First four are all equally first. Others follow in order of priority.] Patch well-known proxies to make them OR compliant Data stream anonymizing, HTTP/FTP (Privoxy, Squid), SMTP, etc. Packet Redirector, a la FreeBSD (DNS, authenticated connections, etc.) Deploy and manage open source development site. Manage and maintain code, write documentation, design and write unit tests, handle patch submissions, make the autoconf work, etc Deploy a widespread network: manage deployment. Maintain and distribute directory/network state information etc. Keep operators and users happy. Test OR network for reliability and performance, with and without mechanisms for throttling, congestion control, padding, load balancing if applicable, etc. Use httperf and webload to get some performance stats Modify code as dictated by testing. Develop rendezvous points Implement reply onions Develop location protected servers idea Enhance router twins to do load balancing as well as DoS prevention Develop and deploy automated reputation management, directory servers, and directory/network state monitoring. --- debian / red hat spec file handle starting things as a system daemon transition addr to sin_addr Obvious things I'd like to do that won't break anything: * Abstract out crypto calls, with the eventual goal of moving * Abstract out crypto calls (done), with the eventual goal of moving from openssl to something with a more flexible license. * Test suite. We need one. Loading
src/or/Makefile.am +3 −3 Original line number Diff line number Diff line Loading @@ -3,11 +3,11 @@ TESTS = test_config noinst_PROGRAMS = test_config bin_PROGRAMS = tor bin_PROGRAMS = or tor_LDADD = -L../common -lor or_LDADD = -L../common -lor tor_SOURCES = buffers.c cell.c circuit.c command.c connection.c \ or_SOURCES = buffers.c cell.c circuit.c command.c connection.c \ connection_exit.c connection_ap.c connection_op.c connection_or.c config.c \ main.c onion.c routers.c Loading