- tor-commits - lists.torproject.org

r25506: {website} Removing unresponsive people from listing of project mentors (website/trunk/getinvolved/en)
by Damian Johnson 05 Mar '12

05 Mar '12

Author: atagar Date: 2012-03-05 16:48:03 +0000 (Mon, 05 Mar 2012) New Revision: 25506 Modified: website/trunk/getinvolved/en/volunteer.wml Log: Removing unresponsive people from listing of project mentors Over a week back I asked everyone listed as potential mentors if they could do it again this year and if their projects were still relevant. Most people replied but a few, understandably were too busy to do so. This included Erinn, Nick, Nathan, and Robert Hogan. Removing them as being potential mentors and dropping the projects that they were the sole mentor for. This included... * Improve our unit testing process (Nick, Erinn) * Simulator for slow Internet connections (Nick) * Make torsocks/dsocks work on OS X (Robert Hogan) * Orbot integration library and community outreach (Nathan) We can add them back later on if they change their minds. Modified: website/trunk/getinvolved/en/volunteer.wml =================================================================== --- website/trunk/getinvolved/en/volunteer.wml 2012-03-05 16:35:03 UTC (rev 25505) +++ website/trunk/getinvolved/en/volunteer.wml 2012-03-05 16:48:03 UTC (rev 25506) @@ -298,9 +298,7 @@ Project Ideas: <a href="#resistCensorship">Improving Tor's ability to resist - censorship</a> - <a href="#unitTesting">Improve our unit testing process</a> - <a href="#simulateSlowConnections">Simulator for slow Internet connections</a> + censorship</a> <a id="project-jtor"></a> @@ -367,10 +365,12 @@ otherwise feature complete. +  <a id="project-torouter"></a> <h3><a @@ -437,8 +437,7 @@ Project Ideas: <a href="#orbot-torbutton">TorButton for Mobile Firefox 4 or Custom Browser on Android</a> <a href="#orbot-userInterface">Build a better user interface for Orbot</a> - <a href="#orbot-optimisation">Core Tor mobile optimisation</a> - <a href="#orbot-orlibAndOutreach">Orbot integration library and community outreach</a> + <a href="#orbot-optimisation">Core Tor mobile optimisation</a> <a id="project-torbutton"></a> @@ -675,7 +674,7 @@ Skill Level: Medium - Likely Mentors: Erinn and Jacob + Likely Mentors: Jacob The Tor Browser Bundle incorporates Tor, Firefox, Polipo, and the Vidalia user interface (and optionally the <a href="http://pidgin.im/">Pidgin</a> Instant Messaging client). Components are pre-configured to operate in a @@ -688,8 +687,6 @@ Students should be familiar with operating system analysis, application development on one or preferably all of Windows, Linux, and Mac OS X, and be comfortable with C/C++ and shell scripting. - If you would like to help extend or do security auditing for - TBB, please contact Erinn. </li> <a id="firewallProbeTool"></a> @@ -702,7 +699,7 @@ Skill Level: High - Likely Mentors: Robert Ransom, Nick, Jacob + Likely Mentors: Robert Ransom, Jacob We would like to have a fully automatic firewall-probing system for blocking systems with no long-term state (i.e. firewalls that can examine each connection, but do not change their behaviour for future @@ -732,7 +729,7 @@ Skill Level: High - Likely Mentors: Nathan (n8fr8), Jake + Likely Mentors: Jake Initial work has been done on implementing a proxy-setting add-on for Firefox on Android (see <a href="https://github.com/guardianproject/ProxyMob">ProxyMob</a>), but a @@ -858,7 +855,7 @@ Skill Level: Medium - Likely Mentors: Nathan (n8fr8), Jake + Likely Mentors: Jake Improved home screen to show confirmation of connection (via a TorCheck API call), better statistics about data transferred (up/down), number of circuits connected, quality of connection and so on. The "Tether @@ -884,7 +881,7 @@ Skill Level: High - Likely Mentors: Nick, Jake, Thomas + Likely Mentors: Jake, Thomas The Tor 0.2.1.x series makes <a href="<svnprojects>design-paper/blocking.html">significant improvements</a> in resisting national and organizational censorship. @@ -1177,6 +1174,7 @@ Applications for this project should come with a design of the proposed search application, ideally with a proof-of-concept based on a subset of the available data to show that it will be able to handle the 100G+ of data. +  +  <a id="torbuttonForThunderbird"></a> <li> @@ -1284,6 +1285,7 @@ </li> +  <a id="vidaliaStatusEventInterface"></a> <li> @@ -1366,7 +1369,7 @@ Skill Level: High - Likely Mentors: Nathan (n8fr8), Jake + Likely Mentors: Jake The existing port of Tor to Android is basically a straight cross-compile to Linux ARM. There has been no work done in looking at @@ -1399,6 +1402,7 @@ </li> +  <!-- <a id="vidaliaNetworkMap"></a>

1 0

r25505: {website} Dropping Mike as a primary mentor from 'TorButton for Mobile (website/trunk/getinvolved/en)
by Damian Johnson 05 Mar '12

05 Mar '12

Author: atagar Date: 2012-03-05 16:35:03 +0000 (Mon, 05 Mar 2012) New Revision: 25505 Modified: website/trunk/getinvolved/en/volunteer.wml Log: Dropping Mike as a primary mentor from 'TorButton for Mobile Firefox 4' Mike is juggling too many things right now to be a primary mentor. At the moment we're trying to figure out if there's an alternate mentor for the thunderbird idea - after that I'll remove him from that one too. Modified: website/trunk/getinvolved/en/volunteer.wml =================================================================== --- website/trunk/getinvolved/en/volunteer.wml 2012-03-05 16:10:18 UTC (rev 25504) +++ website/trunk/getinvolved/en/volunteer.wml 2012-03-05 16:35:03 UTC (rev 25505) @@ -732,7 +732,7 @@ Skill Level: High - Likely Mentors: Nathan (n8fr8), Jake, Mike Perry + Likely Mentors: Nathan (n8fr8), Jake Initial work has been done on implementing a proxy-setting add-on for Firefox on Android (see <a href="https://github.com/guardianproject/ProxyMob">ProxyMob</a>), but a

1 0

r25504: {website} Raising priority of my project idea I should stop flagging e (website/trunk/getinvolved/en)
by Damian Johnson 05 Mar '12

05 Mar '12

Author: atagar Date: 2012-03-05 16:10:18 +0000 (Mon, 05 Mar 2012) New Revision: 25504 Modified: website/trunk/getinvolved/en/volunteer.wml Log: Raising priority of my project idea I should stop flagging everything that I work on as 'medium'. If some of these other projects can be flagged as being a 'high' priority then I can flag mine that way too. It's certianly high priority to me. ;) Modified: website/trunk/getinvolved/en/volunteer.wml =================================================================== --- website/trunk/getinvolved/en/volunteer.wml 2012-03-05 16:06:24 UTC (rev 25503) +++ website/trunk/getinvolved/en/volunteer.wml 2012-03-05 16:10:18 UTC (rev 25504) @@ -791,6 +791,63 @@ href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/190-shared-s…">190</a>. </li> + <a id="stemPathsupport"></a> + <li> + Stem PathSupport Capabilities + + Priority: High + + Effort Level: High + + Skill Level: Medium + + Likely Mentors: Damian (atagar) + <a + href="https://trac.torproject.org/projects/tor/wiki/doc/stem">Stem</a> is a + python controller library for tor. Like it's predecessor, <a + href="#project-torctl">TorCtl</a>, it uses tor's <a + href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/control-spec.txt">control + protocol</a> to help developers program against the tor process, enabling + them to build things similar to <a href="#project-vidalia">Vidalia</a> and + <a href="#project-arm">arm</a>. + + While TorCtl provided a fine first draft for this sort of functionality, + it has not proved to be extensible nor maintainable. Stem is a rewrite of + TorCtl with a heavy focus on testing, documentation, and providing a + developer friendly API. + + At the moment stem is still very much incomplete, missing several pieces + of functionality that TorCtl provides. This is a project to fix that by + porting TorCtl's <a + href="https://gitweb.torproject.org/pytorctl.git/blob/HEAD:/PathSupport.py">PathSupport + module</a> to stem, writing tests for it, and migrate a couple clients to + use it. + + PathSupport provides applications with programmatic control over how + tor's circuits are built, for instance letting you exit from particular + relays. This is used by projects like <a href="#project-torbel">TorBEL</a>, + <a href="#project-torflow">the Bandwidth Scanners, and SoaT</a>. + + This project can be broken into three parts... + + <ol style="list-style-type: decimal"> + <li>Look at PathSupport's clients to figure out how it is used and + come up with the API that we will use for stem. Note that the goal if + this project is not to simply copy PathSupport, but to make it + better. This task would ideally be done as part of writing the GSoC + application.</li> + <li>Implement the PathSupport counterpart for stem. This should be + done in an incremental fashion, writing the feature, tests, and going + through a code review before moving on. I'll be pretty anal about making + it as good as we can during these code reviews so plan for this to take a + while. ;)</li> + <li>The real test of the API that you've developed will come when we + use it in some real applications. Try to migrate a TorCtl client or two + to stem, filling in functionality that we're missing and improving our + API as we discover issues. A particularly good client to start with would + be TorBEL.</li> + </ol> + <a id="orbot-userInterface"></a> <li> Build a better user interface for Orbot @@ -901,63 +958,6 @@ Python using similar tools. </li> - <a id="stemPathsupport"></a> - <li> - Stem PathSupport Capabilities - - Priority: Medium - - Effort Level: High - - Skill Level: Medium - - Likely Mentors: Damian (atagar) - <a - href="https://trac.torproject.org/projects/tor/wiki/doc/stem">Stem</a> is a - python controller library for tor. Like it's predecessor, <a - href="#project-torctl">TorCtl</a>, it uses tor's <a - href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/control-spec.txt">control - protocol</a> to help developers program against the tor process, enabling - them to build things similar to <a href="#project-vidalia">Vidalia</a> and - <a href="#project-arm">arm</a>. - - While TorCtl provided a fine first draft for this sort of functionality, - it has not proved to be extensible nor maintainable. Stem is a rewrite of - TorCtl with a heavy focus on testing, documentation, and providing a - developer friendly API. - - At the moment stem is still very much incomplete, missing several pieces - of functionality that TorCtl provides. This is a project to fix that by - porting TorCtl's <a - href="https://gitweb.torproject.org/pytorctl.git/blob/HEAD:/PathSupport.py">PathSupport - module</a> to stem, writing tests for it, and migrate a couple clients to - use it. - - PathSupport provides applications with programmatic control over how - tor's circuits are built, for instance letting you exit from particular - relays. This is used by projects like <a href="#project-torbel">TorBEL</a>, - <a href="#project-torflow">the Bandwidth Scanners, and SoaT</a>. - - This project can be broken into three parts... - - <ol style="list-style-type: decimal"> - <li>Look at PathSupport's clients to figure out how it is used and - come up with the API that we will use for stem. Note that the goal if - this project is not to simply copy PathSupport, but to make it - better. This task would ideally be done as part of writing the GSoC - application.</li> - <li>Implement the PathSupport counterpart for stem. This should be - done in an incremental fashion, writing the feature, tests, and going - through a code review before moving on. I'll be pretty anal about making - it as good as we can during these code reviews so plan for this to take a - while. ;)</li> - <li>The real test of the API that you've developed will come when we - use it in some real applications. Try to migrate a TorCtl client or two - to stem, filling in functionality that we're missing and improving our - API as we discover issues. A particularly good client to start with would - be TorBEL.</li> - </ol> - <a id="tailsServer"></a> <li> Tails server: Self-hosted services behind Tails-powered Tor hidden services

1 0

r25503: {website} Adding tails' new gsoc projects Couple projects sent by intr (website/trunk/getinvolved/en)
by Damian Johnson 05 Mar '12

05 Mar '12

Author: atagar Date: 2012-03-05 16:06:24 +0000 (Mon, 05 Mar 2012) New Revision: 25503 Modified: website/trunk/getinvolved/en/volunteer.wml Log: Adding tails' new gsoc projects Couple projects sent by intrigeri... * Petname system for Tor hidden services (ague) * Tails server: Self-hosted services behind Tails-powered Tor hidden services (intrigeri, anonym) Modified: website/trunk/getinvolved/en/volunteer.wml =================================================================== --- website/trunk/getinvolved/en/volunteer.wml 2012-03-05 15:41:00 UTC (rev 25502) +++ website/trunk/getinvolved/en/volunteer.wml 2012-03-05 16:06:24 UTC (rev 25503) @@ -347,17 +347,13 @@ and still under very active development. -  <a id="project-torsocks"></a> <h3><a href="http://code.google.com/p/torsocks/">Torsocks</a> (<a @@ -862,6 +858,49 @@ robustness. </li> + <a id="tailsHiddenServicePetnames"></a> + <li> + Petname system for Tor hidden services + + Priority: Medium + + Effort Level: High + + Skill Level: High + + Likely Mentors: ague + Tor provides hidden services. These services are only reachable through + Tor itself, and provide greater anonymity both for the providers of the + service and for its users. + One current downside of Tor hidden services is that they are addressed + using 80-bit base32-encoded addresses such as "v2cbb2l4lsnpio4q.onion". + These addresses are hard to remember; this makes them hard to use + within amnesic environment like Tails. + The project is to implement a petname system for Tor hidden services: + a way for users or providers of Tor hidden services to add a simple + 'nickname' to a central database. Users could then query this central + database to retrieve a full hidden service address by giving + a nickname. + Adding petnames to the database could be done using a web interface or + automated fetch like those described in the <a + href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/ideas/xxx-on…">".onion + nym system" proposal</a>. + Querying the database could be done using a web interface, a REST API and + a DNS interface. + In order not to grow indefinitely, the software should make regular tests to + see if hidden services are still reachable and, depending on the last time + a nickname was accessed, cleanup the database as necessary. + The software should allow a distributed, fault-tolerant setup. + All nodes should have a synchronized copy of the database, should be + ready to answer queries and should coordinate the tests for hidden + service availability. + The resulting codebase must be easy to deploy: it should not be hard to + setup new databases. + It is expected that the volunteer will be using Behaviour Driven + Development methods. Either in Ruby using Cucumber and RSpec, or in + Python using similar tools. + </li> + <a id="stemPathsupport"></a> <li> Stem PathSupport Capabilities @@ -919,6 +958,93 @@ be TorBEL.</li> </ol> + <a id="tailsServer"></a> + <li> + Tails server: Self-hosted services behind Tails-powered Tor hidden services + + Priority: Medium + + Effort Level: High + + Skill Level: Medium, but wide-scoped + + Likely Mentors: intrigeri, anonym + Let's talk about group collaboration, communication and data sharing + infrastructure, such as chat servers, wikis, or file repositories. + Hosting such data and infrastructure in the cloud generally + implies to trust the service providers not to disclose content, usage or + users location information to third-parties. Hence, there are many threat + models in which cloud hosting is not suitable. + Tor partly answers the users location part; this is great, but + content is left unprotected. + There are two main ways to protect such content: either to encrypt it + client-side (security by design), or to avoid putting it into + untrusted hands in the first place. + Cloud solutions that offer security by design are rare and generally + not mature yet. The Tails server project is about exploring the + other side of the alternative: avoiding to put private data into + untrusted hands in the first place. + This is made possible thanks to Tor hidden services, that allow users + to offer location-hidden services, and make self-hosting possible in + many threat models. Self-hosting has its own lot of problems, however, + particularly in contexts where the physical security of the hosting + place is not assured. Combining Tor hidden services with Tails' + amnesia property and limited support for persistent encrypted data + allows to protect content, to a great degree, even in such contexts. + In short, setting up a new Tails server would be done by: + + <ol style="list-style-type: decimal"> + <li>Alice plugs a USB stick into a running desktop Tails system.</li> + <li>Alice uses a GUI to easily configure the needed services.</li> + <li>Alice unplugs the USB stick, that now contains encrypted services + configuration and data storage space.</li> + <li>Alice plugs that USB stick (and possibly a Tails Live CD) into the + old laptop that was dedicated to run Tails server.</li> + <li>Once booted, Alice enters the encryption passphrase either + directly using the keyboard or through a web interface listening on the + local network.</li> + <li>Then, Bob can use the configured services once he gets a hold on + the hidden service address. (The petname system for Tor hidden + services project would be very complementary to this one, by the + way.)</li> + </ol> + + Tails server should content itself with hardware that is a bit old + (such as a PIII-450 laptop with 256MB of RAM) and/or half broken (e.g. + non-functional hard-disk, screen or keyboard). + The challenges behind this project are: + + <ul> + <li>Design and write the services configuration GUI [keywords: edit + configuration files, upgrade between major Debian versions, + debconf].</li> + <li>How to create the hidden service key? [keywords: Vidalia, control + protocol].</li> + <li>Adapt the Tails boot process to allow switching to "server + mode" when appropriate.</li> + <li>Add support, to the Tails persistence setup process, for asking an + encryption passphrase without X, and possibly with a broken keyboard + and/or screen [keywords: local network, SSL/TLS?, certificate?].</li> + </ul> + + This project can easily grow quite large, so the first task would + probably be to clarify what it would need to get an initial (minimal + but working) implementation ready to be shipped to users. + This project does not require to be an expert in one specific field, + but it requires to be experienced and at ease with a large scope of + software development tools, processes, and operating system knowledge. + Undertaking this project requires in-depth knowledge of Debian-like + systems (self-test: do the "dpkg conffile" and "debconf preseeding" + words sound new to your ear?); the Debian Live persistence system + being written in shell, being at ease with robust shell scripting is + a must; to end with, at least two pieces of software need to be + written from scratch (a GUI and a webapp): the preferred languages for + these tasks would be Python and Perl. Using Behaviour Driven + Development methods to convey expectations and acceptance criteria + would be most welcome. + For more information see https://tails.boum.org/todo/server_edition/ + </li> + <a id="geoIPUpgrade"></a> <li> Improve our GeoIP file format

1 0

[tor/master] Set IPV6_V6ONLY on listener sockets bound to IPv6 addresses.
by nickm＠torproject.org 05 Mar '12

05 Mar '12

commit dd68d596cdf68999c0cb4c0caf594d8580eaba40 Author: Nick Mathewson <nickm(a)torproject.org> Date: Tue Jan 31 16:09:49 2012 -0500 Set IPV6_V6ONLY on listener sockets bound to IPv6 addresses. If we don't do this, [::] can be interpreted to mean all v4 and all v6 addresses. Found by dcf. Fixes bug 4760. See RFC 3493 section 5.3 for more info. --- changes/bug4760 | 4 ++++ src/or/connection.c | 19 +++++++++++++++++++ 2 files changed, 23 insertions(+), 0 deletions(-) diff --git a/changes/bug4760 b/changes/bug4760 new file mode 100644 index 0000000..ea8d16e --- /dev/null +++ b/changes/bug4760 @@ -0,0 +1,4 @@ + o Minor bugfixes: + - When binding to an IPv6 address, set the IPV6_V6ONLY socket + option, so that the IP stack doesn't decide to use it for IPv4 + too. Fixes bug 4760; bugfix on 0.2.3.9-alpha. diff --git a/src/or/connection.c b/src/or/connection.c index bf65e8e..06a7562 100644 --- a/src/or/connection.c +++ b/src/or/connection.c @@ -902,6 +902,25 @@ connection_listener_new(const struct sockaddr *listensockaddr, make_socket_reuseable(s); +#ifdef IPV6_V6ONLY + if (listensockaddr->sa_family == AF_INET6) { +#ifdef _WIN32 + /* In Redmond, this kind of thing passes for standards-conformance. */ + DWORD one = 1; +#else + int one = 1; +#endif + /* We need to set IPV6_V6ONLY so that this socket can't get used for + * IPv4 connections. */ + if (setsockopt(s,IPPROTO_IPV6, IPV6_V6ONLY, (void*)&one, sizeof(one))<0) { + int e = tor_socket_errno(s); + log_warn(LD_NET, "Error setting IPV6_V6ONLY flag: %s", + tor_socket_strerror(e)); + /* Keep going; probably not harmful. */ + } + } +#endif + if (bind(s,listensockaddr,socklen) < 0) { const char *helpfulhint = ""; int e = tor_socket_errno(s);

1 0

[tor/master] Merge remote-tracking branch 'public/bug4760'
by nickm＠torproject.org 05 Mar '12

05 Mar '12

commit 298e08132f3368514b868eecc5f44e982280010d Merge: 77a7a98 dd68d59 Author: Nick Mathewson <nickm(a)torproject.org> Date: Mon Mar 5 10:44:48 2012 -0500 Merge remote-tracking branch 'public/bug4760' changes/bug4760 | 4 ++++ src/or/connection.c | 19 +++++++++++++++++++ 2 files changed, 23 insertions(+), 0 deletions(-)

1 0

r25502: {website} Dropping last year's tails projects Checked with intrigeri a (website/trunk/getinvolved/en)
by Damian Johnson 05 Mar '12

05 Mar '12

Author: atagar Date: 2012-03-05 15:41:00 +0000 (Mon, 05 Mar 2012) New Revision: 25502 Modified: website/trunk/getinvolved/en/volunteer.wml Log: Dropping last year's tails projects Checked with intrigeri and the prior three tails projects are no longer relevant. He sent replacements that I'll add in a sec. Modified: website/trunk/getinvolved/en/volunteer.wml =================================================================== --- website/trunk/getinvolved/en/volunteer.wml 2012-03-03 19:47:35 UTC (rev 25501) +++ website/trunk/getinvolved/en/volunteer.wml 2012-03-05 15:41:00 UTC (rev 25502) @@ -347,6 +347,7 @@ and still under very active development. +  <a id="project-torsocks"></a> <h3><a href="http://code.google.com/p/torsocks/">Torsocks</a> (<a @@ -724,35 +726,6 @@ </ul> </li> - <a id="tailsStartMenu"></a> - <li> - Custom GDM3 startup menu, aka. tails-greeter - - Priority: High - - Effort Level: Medium - - Skill Level: Medium to High - - Likely Mentors: intrigeri, anonym - Several major upcoming Tails features need to gather user input at - startup time: bridges support, persistence, MAC address anonymization, - etc. - Existing boot menus lack the graphical widgets and generally - user-friendliness needed. Hence it was decided to implement Tails startup - menu in GDM3: GDM3's default login/password prompt needs to be replaced - with a custom GTK+ application hereby named tails-greeter that allows the - user to provide any input necessary. - Anyone undertaking this project should be familiar with GNU/Linux and - application development; no other skill is required, apart of the ability - to quickly find practical answers in APIs and documentation for many - technologies she knows nothing about: this challenging coding project will - indeed involve getting familiar with some modern GNU/Linux Desktop - technologies such as D-Bus, GNOME and GConf. Python/GTK+ is probably the - best suited language for the task. - For more information see <a href="https://tails.boum.org/todo/boot_menu/">https://tails.boum.org/todo/boot_menu/</a> - </li> - <a id="orbot-torbutton"></a> <li> TorButton for Mobile Firefox 4 or Custom Browser on Android @@ -1185,68 +1158,6 @@ </li> - <a id="tailsMetadataAnonymizing"></a> - <li> - Meta-data anonymizing toolkit for file publication - - Priority: Medium - - Effort Level: Low to Medium - - Skill Level: Low to Medium - - Likely Mentors: intrigeri, anonym - Tor helps greatly in publishing files anonymously. However, much personal - information can be enclosed *inside* such published files' meta-data: GPS - coordinates, author's name and so on. Anyone who wants to anonymously - publish a file can thus far too easily de-anonymize herself. - A set of tools allowing users to easily inspect and clean up meta-data in files - would benefit Tor users, and would e.g. be shipped in Tails. - A graphical user interface is a must, but library and command-line - interfaces are most welcome so that future work can add support for - cleaning published files to various publishing tools, such as desktop - social networking clients and Web content management systems. - This project mostly consists of writing glue between the many existing - tools and libraries that provide read/write access to files' meta-data. An - extensible program design would probably be the best bet, so that support - for other kinds of files can easily be added later. - The meta-data cleaning toolkit would run at least on GNU/Linux; - additional Windows and/or Mac OS X support would be welcome. The tools used - would be up to the students. The detailed specification is ready and will - be published soon. - </li> - - <a id="tailsDebianLive"></a> - <li> - Improve Debian Live support for persistence - - Priority: Medium - - Effort Level: Medium - - Skill Level: Low to Medium - - Likely Mentors: intrigeri, anonym - Data persistence is a somewhat tricky topic in a Live system context, - especially one such as Tails, which is explicitly designed to avoid - leaving any trace of its use. - Some real-life use cases, however, require some kind of data - persistence. To start with, Tails should (carefully) support persistence of - application-specific configurations (e.g. GnuPG keyring) and of a user - arbitrary data store. Note that persistence in Tails will always be opt-in - and require encrypted storage. - The backend work consists of improving Debian Live's existing - persistence features to make them suit the specific context of Tails. A trust - relationship is already established with upstream who is happy to merge our - changes. The codebase is not that small and much refactoring is needed, so - this really is a programming project rather than a fire'n'forget shell - script hack contest. - Anyone undertaking this project must be familiar with GNU/Linux, and - preferably with Debian. Being able to (quickly learn to) write clean and - safe programs in shell is also needed. - For more information, see <a href="https://tails.boum.org/todo/persistence/">https://tails.boum.org/todo/persistence/</a>. - </li> - <a id="torsocksForOSX"></a> <li> Make torsocks/dsocks work on OS X

1 0

[torperf/master] Lenny is dead.
by karsten＠torproject.org 05 Mar '12

05 Mar '12

commit 3cea734b10b5a8276771adbdd1425f71df1c6e42 Author: Karsten Loesing <karsten.loesing(a)gmx.net> Date: Mon Mar 5 16:18:21 2012 +0100 Lenny is dead. --- measurements-HOWTO | 27 +++------------------------ 1 files changed, 3 insertions(+), 24 deletions(-) diff --git a/measurements-HOWTO b/measurements-HOWTO index e8978e3..67de0c5 100644 --- a/measurements-HOWTO +++ b/measurements-HOWTO @@ -116,31 +116,10 @@ $ ./start-tors Install the timeout tool: -$ sudo apt-get install timeout # Lenny -$ sudo apt-get install coreutils # Squeeze +$ sudo apt-get install coreutils -Add crontab entries to start the regular requests. - -Note that the syntax of the timeout script in Lenny is different from the -one in Squeeze. When in doubt, look up the correct syntax in the man -page. For the timeout script contained in Lenny, the crontab entries -would be as follows (line breaks are only for formatting purposes here): - -$ crontab -e - -*/5 * * * * timeout -2 295 ~/torperf/trivsocks-client - torperf.torproject.org 127.0.0.1:9020 /.50kbfile >> ~/torperf/50kb.data - 2>/dev/null -2,32 * * * * timeout -2 1795 ~/torperf/trivsocks-client - torperf.torproject.org 127.0.0.1:9021 /.1mbfile >> ~/torperf/1mb.data - 2>/dev/null -8 * * * * timeout -2 3595 ~/torperf/trivsocks-client - torperf.torproject.org 127.0.0.1:9022 /.5mbfile >> ~/torperf/5mb.data - 2>/dev/null - -For the timeout script in Squeeze, use the following crontab entries (the -only difference is that the first command-line argument is "-s2" instead -of "-2"; again, line breaks for formatting purposes only): +Add crontab entries to start the regular requests (line breaks are only +for formatting purposes here): $ crontab -e

1 0

[vidalia/master] Version bump to 0.2.18-git
by chiiph＠torproject.org 05 Mar '12

05 Mar '12

commit f3e364450f41028197ad39f644acd793cc1c4bf0 Author: Tomás Touceda <chiiph(a)torproject.org> Date: Mon Mar 5 09:38:03 2012 -0300 Version bump to 0.2.18-git --- CMakeLists.txt | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/CMakeLists.txt b/CMakeLists.txt index be764ce..498041c 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -13,8 +13,8 @@ set(VER_MAJOR "0") set(VER_MINOR "2") -set(VER_PATCH "17") -set(VERSION "${VER_MAJOR}.${VER_MINOR}.${VER_PATCH}") +set(VER_PATCH "18") +set(VERSION "${VER_MAJOR}.${VER_MINOR}.${VER_PATCH}-git") message(STATUS "Configuring Vidalia ${VERSION}") project(Vidalia)

1 0

[vidalia/master] Add a changes file for the microdescriptors support
by chiiph＠torproject.org 05 Mar '12

05 Mar '12

commit cfb1377b5dc2b5ec221e11e8df5137c476c6e744 Author: Tomás Touceda <chiiph(a)torproject.org> Date: Mon Mar 5 09:45:50 2012 -0300 Add a changes file for the microdescriptors support --- changes/bug4203 | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/changes/bug4203 b/changes/bug4203 new file mode 100644 index 0000000..e92852e --- /dev/null +++ b/changes/bug4203 @@ -0,0 +1 @@ + o Add support for Microdescriptors. Fixes ticket 4203. \ No newline at end of file

1 0