January 2020 - tor-commits - lists.torproject.org

[tor/master] Merge branch 'tor-github/pr/1687'
by dgoulet＠torproject.org 30 Jan '20

30 Jan '20

commit 1bf377f4b68136a238d9e54d5b56169c9589b583 Merge: f07d8a1a9 3208a74f9 Author: David Goulet <dgoulet(a)torproject.org> Date: Thu Jan 30 14:06:09 2020 -0500 Merge branch 'tor-github/pr/1687' contrib/client-tools/tor-resolve.py | 10 +++++----- scripts/codegen/gen_server_ciphers.py | 14 +++++++------- scripts/codegen/get_mozilla_ciphers.py | 8 ++++---- scripts/codegen/makedesc.py | 15 ++++++++++----- scripts/maint/format_changelog.py | 2 +- scripts/maint/locatemissingdoxygen.py | 6 +++--- scripts/maint/redox.py | 17 +++++++++++------ src/ext/ed25519/ref10/base.py | 14 +++++++------- src/ext/ed25519/ref10/base2.py | 10 +++++----- src/ext/ed25519/ref10/d.py | 2 +- src/ext/ed25519/ref10/d2.py | 2 +- src/ext/ed25519/ref10/sqrtm1.py | 2 +- src/test/ed25519_exts_ref.py | 20 ++++++++++---------- 13 files changed, 66 insertions(+), 56 deletions(-)

1 0

[tor/master] changes: file for 33091
by dgoulet＠torproject.org 30 Jan '20

30 Jan '20

commit f3ecf0b0a4ac406cc03f76606c95e1ccf636cca3 Author: teor <teor(a)torproject.org> Date: Wed Jan 29 18:27:53 2020 +1000 changes: file for 33091 --- changes/ticket33091 | 3 +++ 1 file changed, 3 insertions(+) diff --git a/changes/ticket33091 b/changes/ticket33091 new file mode 100644 index 000000000..89efd9089 --- /dev/null +++ b/changes/ticket33091 @@ -0,0 +1,3 @@ + o Code simplification and refactoring (mainloop): + - Simplify the ip_address_changed() function by removing redundant checks. + Closes ticket 33091.

1 0

[tor/master] mainloop: Simplify ip_address_changed()
by dgoulet＠torproject.org 30 Jan '20

30 Jan '20

commit c8ba2c4730180d9d9889a939855331bb1e9f95ac Author: teor <teor(a)torproject.org> Date: Wed Jan 29 18:23:38 2020 +1000 mainloop: Simplify ip_address_changed() Simplify ip_address_changed() by removing redundant checks (all exits are relays, and need to rebuild their descriptor when their IP addresses change). Rewrite the function comment, and rename the argument, so the function is easier to understand and use. Closes 33091. --- src/core/mainloop/mainloop.c | 30 +++++++++++++++++------------- src/core/mainloop/mainloop.h | 2 +- 2 files changed, 18 insertions(+), 14 deletions(-) diff --git a/src/core/mainloop/mainloop.c b/src/core/mainloop/mainloop.c index 7781b29fb..260de181e 100644 --- a/src/core/mainloop/mainloop.c +++ b/src/core/mainloop/mainloop.c @@ -2273,18 +2273,23 @@ systemd_watchdog_callback(periodic_timer_t *timer, void *arg) #define UPTIME_CUTOFF_FOR_NEW_BANDWIDTH_TEST (6*60*60) -/** Called when our IP address seems to have changed. <b>at_interface</b> - * should be true if we detected a change in our interface, and false if we - * detected a change in our published address. */ +/** Called when our IP address seems to have changed. <b>on_client_conn</b> + * should be true if: + * - we detected a change in our interface address, using an outbound + * connection, and therefore + * - our client TLS keys need to be rotated. + * Otherwise, it should be false, and: + * - we detected a change in our published address + * (using some other method), and therefore + * - the published addresses in our descriptor need to change. + */ void -ip_address_changed(int at_interface) +ip_address_changed(int on_client_conn) { const or_options_t *options = get_options(); int server = server_mode(options); - int exit_reject_interfaces = (server && options->ExitRelay - && options->ExitPolicyRejectLocalInterfaces); - if (at_interface) { + if (on_client_conn) { if (! server) { /* Okay, change our keys. */ if (init_keys_client() < 0) @@ -2296,15 +2301,14 @@ ip_address_changed(int at_interface) reset_bandwidth_test(); reset_uptime(); router_reset_reachability(); + /* All relays include their IP addresses as their ORPort addresses in + * their descriptor. + * Exit relays also incorporate interface addresses in their exit + * policies, when ExitPolicyRejectLocalInterfaces is set. */ + mark_my_descriptor_dirty("IP address changed"); } } - /* Exit relays incorporate interface addresses in their exit policies when - * ExitPolicyRejectLocalInterfaces is set */ - if (exit_reject_interfaces || (server && !at_interface)) { - mark_my_descriptor_dirty("IP address changed"); - } - dns_servers_relaunch_checks(); } diff --git a/src/core/mainloop/mainloop.h b/src/core/mainloop/mainloop.h index f9a48a8e0..1ddfec216 100644 --- a/src/core/mainloop/mainloop.h +++ b/src/core/mainloop/mainloop.h @@ -56,7 +56,7 @@ MOCK_DECL(int, connection_count_moribund, (void)); void directory_all_unreachable(time_t now); void directory_info_has_arrived(time_t now, int from_cache, int suppress_logs); -void ip_address_changed(int at_interface); +void ip_address_changed(int on_client_conn); void dns_servers_relaunch_checks(void); void reset_all_main_loop_timers(void); void reschedule_directory_downloads(void);

1 0

[tor/master] connection: Improve function comments
by dgoulet＠torproject.org 30 Jan '20

30 Jan '20

commit d873674fb37342285e712da054398fab23cb0091 Author: teor <teor(a)torproject.org> Date: Wed Jan 29 18:22:21 2020 +1000 connection: Improve function comments Improve the function comments on connection_finished_connecting(), to describe what the function actually does. Part of 33091. --- src/core/mainloop/connection.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/core/mainloop/connection.c b/src/core/mainloop/connection.c index 223428a8f..4a2dc21f1 100644 --- a/src/core/mainloop/connection.c +++ b/src/core/mainloop/connection.c @@ -4970,10 +4970,10 @@ connection_finished_flushing(connection_t *conn) } } -/** Called when our attempt to connect() to another server has just - * succeeded. +/** Called when our attempt to connect() to a server has just succeeded. * - * This function just passes conn to the connection-specific + * This function checks if the interface address has changed (clients only), + * and then passes conn to the connection-specific * connection_*_finished_connecting() function. */ static int

1 0

[tor/master] Merge branch 'tor-github/pr/1692'
by dgoulet＠torproject.org 30 Jan '20

30 Jan '20

commit f07d8a1a92b75d37cc0bd9eb42d45850b8f60e54 Merge: a1dec4472 f3ecf0b0a Author: David Goulet <dgoulet(a)torproject.org> Date: Thu Jan 30 13:53:32 2020 -0500 Merge branch 'tor-github/pr/1692' changes/ticket33091 | 3 +++ src/core/mainloop/connection.c | 6 +++--- src/core/mainloop/mainloop.c | 30 +++++++++++++++++------------- src/core/mainloop/mainloop.h | 2 +- 4 files changed, 24 insertions(+), 17 deletions(-)

1 0

[tor/master] Do not set "once" when calling tor_bug_occurred_ from BUG().
by dgoulet＠torproject.org 30 Jan '20

30 Jan '20

commit 2a1f8ea2e78486966c71762ebc3286f2b3e531ff Author: Nick Mathewson <nickm(a)torproject.org> Date: Thu Jan 30 09:43:34 2020 -0500 Do not set "once" when calling tor_bug_occurred_ from BUG(). The "once" flag makes tor_bug_occurred_() say that future instances of the warning will be suppressed -- but that's not something that BUG() does. Fixes bug 33095; bugfix on 0.4.1.1-alpha. --- changes/bug33095_041 | 5 +++++ src/lib/log/util_bug.h | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/changes/bug33095_041 b/changes/bug33095_041 new file mode 100644 index 000000000..7d1f04e27 --- /dev/null +++ b/changes/bug33095_041 @@ -0,0 +1,5 @@ + o Minor bugfixes (logging, bug reporting): + - When logging a bug, do not say "Future instances of this warning + will be silenced" unless we are actually going to do + so. Previously we would say this whenever a BUG() check failed in + the code. Fixes bug 33095; bugfix on 0.4.1.1-alpha. diff --git a/src/lib/log/util_bug.h b/src/lib/log/util_bug.h index 546ae1e3e..f67c1e995 100644 --- a/src/lib/log/util_bug.h +++ b/src/lib/log/util_bug.h @@ -196,7 +196,7 @@ STMT_END #define BUG(cond) \ (ASSERT_PREDICT_UNLIKELY_(cond) ? \ - (tor_bug_occurred_(SHORT_FILE__,__LINE__,__func__,"!("#cond")",1,NULL),1) \ + (tor_bug_occurred_(SHORT_FILE__,__LINE__,__func__,"!("#cond")",0,NULL),1) \ : 0) #endif /* defined(ALL_BUGS_ARE_FATAL) || ... */

1 0

[tor/master] Merge branch 'tor-github/pr/1697'
by dgoulet＠torproject.org 30 Jan '20

30 Jan '20

commit a1dec44723b4c2b38140b49efd0d30bb784626ae Merge: 9662a13d7 2a1f8ea2e Author: David Goulet <dgoulet(a)torproject.org> Date: Thu Jan 30 13:48:36 2020 -0500 Merge branch 'tor-github/pr/1697' changes/bug33095_041 | 5 +++++ src/lib/log/util_bug.h | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-)

1 0

[tor/master] Fix a changelog typo
by nickm＠torproject.org 30 Jan '20

30 Jan '20

commit 9662a13d7e587ec9b78af77cdb6607b4ad23a918 Author: Nick Mathewson <nickm(a)torproject.org> Date: Thu Jan 30 12:56:06 2020 -0500 Fix a changelog typo --- ChangeLog | 6 +++--- ReleaseNotes | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/ChangeLog b/ChangeLog index 195093a5b..3d05bea86 100644 --- a/ChangeLog +++ b/ChangeLog @@ -9,7 +9,7 @@ Changes in version 0.4.2.6 - 2020-01-30 - Correct how we use libseccomp. Particularly, stop assuming that rules are applied in a particular order or that more rules are processed after the first match. Neither is the case! In - libseccomp <2.4.0 this lead to some rules having no effect. + libseccomp <2.4.0 this led to some rules having no effect. libseccomp 2.4.0 changed how rules are generated, leading to a different ordering, which in turn led to a fatal crash during startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by @@ -64,7 +64,7 @@ Changes in version 0.4.1.8 - 2020-01-30 - Correct how we use libseccomp. Particularly, stop assuming that rules are applied in a particular order or that more rules are processed after the first match. Neither is the case! In - libseccomp <2.4.0 this lead to some rules having no effect. + libseccomp <2.4.0 this led to some rules having no effect. libseccomp 2.4.0 changed how rules are generated, leading to a different ordering, which in turn led to a fatal crash during startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by @@ -146,7 +146,7 @@ Changes in version 0.4.3.1-alpha - 2020-01-22 - Correct how we use libseccomp. Particularly, stop assuming that rules are applied in a particular order or that more rules are processed after the first match. Neither is the case! In - libseccomp <2.4.0 this lead to some rules having no effect. + libseccomp <2.4.0 this led to some rules having no effect. libseccomp 2.4.0 changed how rules are generated, leading to a different ordering, which in turn led to a fatal crash during startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by diff --git a/ReleaseNotes b/ReleaseNotes index c33355f68..7d981e2c4 100644 --- a/ReleaseNotes +++ b/ReleaseNotes @@ -13,7 +13,7 @@ Changes in version 0.4.2.6 - 2020-01-30 - Correct how we use libseccomp. Particularly, stop assuming that rules are applied in a particular order or that more rules are processed after the first match. Neither is the case! In - libseccomp <2.4.0 this lead to some rules having no effect. + libseccomp <2.4.0 this led to some rules having no effect. libseccomp 2.4.0 changed how rules are generated, leading to a different ordering, which in turn led to a fatal crash during startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by @@ -68,7 +68,7 @@ Changes in version 0.4.1.8 - 2020-01-30 - Correct how we use libseccomp. Particularly, stop assuming that rules are applied in a particular order or that more rules are processed after the first match. Neither is the case! In - libseccomp <2.4.0 this lead to some rules having no effect. + libseccomp <2.4.0 this led to some rules having no effect. libseccomp 2.4.0 changed how rules are generated, leading to a different ordering, which in turn led to a fatal crash during startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by

1 0

[snowflake/master] Also show message in the "error copying WebSocket to ORPort" case.
by dcf＠torproject.org 30 Jan '20

30 Jan '20

commit a4287095c05addaa204c605c691f147da477c2f5 Author: David Fifield <david(a)bamsoftware.com> Date: Thu Jan 30 10:15:12 2020 -0700 Also show message in the "error copying WebSocket to ORPort" case. This was the only case out of the three not to show it. --- server/server.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/server/server.go b/server/server.go index 5ed56d3..9023252 100644 --- a/server/server.go +++ b/server/server.go @@ -68,7 +68,7 @@ func proxy(local *net.TCPConn, conn *websocketconn.WebSocketConn) { }() go func() { if _, err := io.Copy(local, conn); err != nil { - log.Printf("error copying WebSocket to ORPort") + log.Printf("error copying WebSocket to ORPort %v", err) } if err := local.CloseWrite(); err != nil { log.Printf("error closing write after copying WebSocket to ORPort %v", err)

1 0

[newsletter/master] Add january newsletter
by hiro＠torproject.org 30 Jan '20

30 Jan '20

commit 5f77ba298238bb9e94cad1fb0aabffe40299597a Author: hiro <hiro(a)torproject.org> Date: Thu Jan 30 17:36:42 2020 +0100 Add january newsletter --- .../contents.lr | 163 +++++++++++++++++++++ .../text/contents.lr | 128 ++++++++++++++++ 2 files changed, 291 insertions(+) diff --git a/content/archive/bug-smash-advocacy-what-we-are-reading-events/contents.lr b/content/archive/bug-smash-advocacy-what-we-are-reading-events/contents.lr new file mode 100644 index 0000000..675c482 --- /dev/null +++ b/content/archive/bug-smash-advocacy-what-we-are-reading-events/contents.lr @@ -0,0 +1,163 @@ +_model: post +--- +_template: newsletter.html +--- +author: steph(a)torproject.org +--- +pub_date: 2020-01-30 +--- +title: Bug Smash, Advocacy, What We're Reading, Events +--- +html_body: + +<table align="center" border="0" cellpadding="0" cellspacing="0" class="devicewidth" width="650"> + <tbody> + <tr> + <td width="100%"> + <table align="center" bgcolor="#ffffff" border="0" cellpadding="0" cellspacing="0" class="devicewidth" width="650"> + <tbody> + <tr> + <td height="20" width="100%"><a href="https://torproject.org"><img alt="tor-news-logo" src="https://blog.torproject.org/sites/default/files/inline-images/tor-news-logo…" style="width: 250px; height: 75px;" /></a></td> + </tr> + <tr> + <td> + <table align="center" border="0" cellpadding="0" cellspacing="0" class="devicewidth" width="650"> + <tbody> + <tr> + <td width="100%"> + <table align="center" bgcolor="#ffffff" border="0" cellpadding="0" cellspacing="0" class="devicewidth" width="650"> + <tbody> + <tr> + <td style="padding:0 15px 15px 15px;"> + <hr /> + <h1>Tor's Bug Smash Fund: Progress So Far</h1> + + <p><a href="https://blog.torproject.org/tor-bug-smash-fund-progress"><img alt="tor bug smash " src="https://blog.torproject.org/sites/default/files/styles/full_width/public/im…" style="width: 640px; height: 320px;" /></a></p> + + <p>At the beginning of August 2019, we asked you to help us build <a href="https://blog.torproject.org/tors-bug-smash-fund-help-tor-smash-all-bugs">our very first Bug Smash Fund</a>. This fund will ensure that the Tor Project has a healthy reserve earmarked for maintenance work and smashing the bugs necessary to keep Tor Browser, the Tor network, and the <a href="https://blog.torproject.org/strength-numbers-entire-ecosystem-relies-tor">many tools that rely on Tor</a> strong, safe, and running smoothly. Together we raised $86,081.</p> + + <p>So far, we’ve marked 77 tickets with <a href="https://trac.torproject.org/projects/tor/query?status=accepted&status=a…">BugSmashFund</a>. As of today, 56 of those tickets have been closed, and 21 of them are still in progress. With this reserve, we’ve been able to fix bugs and complete necessary maintenance on core tor, bridgedb, Snowflake, and Metrics, as well as complete the Tor Browser ESR 68 migration. Roughly half of the Bug Smash Fund remains available for allocation, and we will continue to tag relevant maintenance work and bug fixing tickets that will be covered with this reserve. <a href="https://blog.torproject.org/ tor-bug-smash-fund-progress">Take a look at the tickets we've closed so far</a>.</p> + + <hr /> + <h1>Help Stop the Sale of Public Interest Registry to a Private Equity Firm</h1> + + <p><a href="https://act.eff.org/action/help-stop-the-sale-of-public-interest-registry-t…"><img alt=".org" src="https://s3-us-west-1.amazonaws.com/actioncenter/action_pages/featured_image…" style="width: 640px; height: 320px;" /></a></p> + + <p>Last month it was suddenly announced that the nonprofit that owns the .ORG domain registry was planning to sell it to a private equity firm, Ethos Capital. This could impact the millions of individuals and organizations that have a .ORG website, including the Tor Project, subjecting them to potential censorship and leaving the door open for price increases on domain registration and renewals.</p> + + <p><a href="https://act.eff.org/action/help-stop-the-sale-of-public-interest-registry-t…">Please take action today</a> and add your name to the <a href="https://savedotorg.org">twenty-thousand individuals</a> who have opposed the sale.</p> + + <hr /> + <h1 class="page-title"><span class="field field--name-title field--type-string field--label-hidden">Buying a smart phone on the cheap? Privacy might be the price you have to pay</span></h1> + + <p><em>Research by Privacy International shows that cheap smartphones come with a hidden cost: pre-installed apps that can't be deleted and that leak your data.</em></p> + + <p>We're telling Google it's time to take action on pre-installed apps. Add your voice here: <a href="https://privacyinternational.org/petition#phil">privacyinternational.org/petition.</a></p> + + <hr /> + <h1>Privacy isn't about having something to hide.</h1> + + <p><a href="https://twitter.com/torproject/status/1222163716281683970"><img alt="privacy" src="https://pbs.twimg.com/media/EPTLVZqVAAADMzf?format=jpg&name=large" style="width: 640px; height: 360px;" /></a></p> + + <p>We believe technology must b<span class="css-901oao css-16my406 r-1qd0xha r-ad9z0x r-bcqeeo r-qvutc0">e designed in an ethical way that respects people's digital rights. Privacy cannot be an afterthought <a href="https://www.nytimes.com/2019/12/29/technology/california-privacy-law.html">with room for interpretation</a> by businesses that thrive on exploiting us online. Privacy must be the default. </span></p> + + <hr /> + <h1 class="title"><span class="quickedit-field" data-quickedit-field-id="node/1814/title/en/teaser" property="schema:name">What We're Reading</span></h1> + + <h2 class="css-1qskr30 e1h9rw200" itemprop="headline"><span class="balancedHeadline" style="display: inline-block; max-width: 547.633px;">"Reporters Face New Threats From the Governments They Cover," James Risen, <a href="https://www.nytimes.com/2020/01/26/opinion/greenwald-brazil-reporter.html">The New York Times</a>. [<a href="https://www.nytimes3xbfgragh.onion/2020/01/26/opinion/greenwald-brazil-repo…">.onion</a>]</span></h2> + + <p>"Both the Trump administration and the right-wing Brazilian government of President Jair Bolsonaro seem to have decided to experiment with such draconian anti-press tactics..."</p> + + <h2 class="ez fa eo fb eq fc es fd eu fe ew ff em">"The Trump Administration’s Lies About Encryption Are Putting Our Privacy in Danger," <a href="https://gen.medium.com/the-trump-administrations-lies-about-encryption-are-…">Trevor Timm</a>.</h2> + + <p>"The Trump administration is now engaged in a multipronged effort to pressure tech companies to weaken encryption protecting the privacy of billions of people. And make no mistake: They are blatantly lying about it to try to get their way."</p> + + <h2>"You Are Now Remotely Controlled," <span class="css-1baulvz last-byline" itemprop="name">Shoshana Zuboff, </span><a href="https://www.nytimes.com/2020/01/24/opinion/sunday/surveillance-capitalism.h…">The New York Times</a>. [<a href="https://www.nytimes3xbfgragh.onion/2020/01/24/opinion/sunday/surveillance-c…">.onion</a>]</h2> + + <p>"Surveillance capitalists exploit the widening inequity of knowledge for the sake of profits. They manipulate the economy, our society and even our lives with impunity, endangering not just individual privacy but democracy itself."</p> + + <hr /> + <h1>New Releases</h1> + + <h2>Tor 0.4.3.1-alpha</h2> + + <p>This is the first alpha release in the 0.4.3.x series. It includes improved support for application integration of onion services, support for building in a client-only mode, and newly improved internal documentation (online at https://src-ref.docs.torproject.org/tor/) It also has numerous other small bugfixes and features, as well as improvements to our code's internal organization that should help us write better code in the future. <a href="https://blog.torproject.org/new-alpha-release-tor-0431-alpha">Full changelog</a>.</p> + + <h2>Tor Browser 9.5a4</h2> + + <p>This new alpha release picks up security fixes for Firefox 68.4.0esr and 68.4.1esr. In addition, this release updates the bundled NoScript extension to its latest version. <span class="css-901oao css-16my406 r-1qd0xha r-ad9z0x r-bcqeeo r-qvutc0"><a href="https://blog.torproject.org/new-release-tor-browser-95a4">Full changelog</a>. </span></p> + + <h2>Tor Browser 9.0.3 & 9.0.4</h2> + + <p>9.0.3 picks up security fixes for Firefox 68.4.0esr. We also updated Tor to 0.4.2.5 for the desktop versions. On Android we fixed a possible crash after the bootstrap. 9.0.4 fixes a <a href="https://www.mozilla.org/en-US/security/advisories/mfsa2020-03/">critical security issue in Firefox</a>: CVE-2019-17026.<a href="https://blog.torproject.org/new-release-tor-browser-903"> </a> <a href="https://blog.torproject.org/new-release-tor-browser-903">Full changelogs for 9.03 & </a><a href="https://blog.torproject.org/new-release-tor-browser-904">9.04</a>.</p> + + <h2>Stem 1.8</h2> + + <p>Stem is a Python library for interacting with Tor. With it you can script against your relay, descriptor data, or even write applications like <a href="https://nyx.torproject.org/">Nyx</a>. <a href="https://blog.torproject.org/new-release-stem-18">Changelog</a>.</p> + + <hr /> + <h1>Upcoming Events with Tor</h1> + + <p class="field field--name-field-event-dates field--type-daterange field--label-hidden field--item quickedit-field" data-quickedit-field-id="node/1728/field_event_dates/en/full"><span class="views-field views-field-title"><span class="field-content"><a href="https://blog.torproject.org/tor-fosdem-2020-brussels" hreflang="en">FOSDEM</a>. Belgium, Brussels</span></span><span class="quickedit-field" data-quickedit-field-id="node/1728/title/en/full">.</span><time datetime="2019-09-12T12:00:00Z"> 1-2 February 2020</time>. <a href="https://fosdem.org/2020/interviews/pili-guerra/">Interview with Tor speaker Pili Guerra</a>.</p> + + <hr /> + <h1>Join Our Community</h1> + + <p>Getting involved with Tor is easy. <a href="https://trac.torproject.org/projects/tor/wiki/TorRelayGuide">Run a relay</a> to make the network faster and more decentralized. <a href="https://blog.torproject.org/run-tor-bridges-defend-open-internet">Run a bridge</a> to help censored users access Tor.</p> + + <p>Learn about each of our <a href="https://trac.torproject.org/projects/tor/wiki/WikiStart#Teams">teams </a>and start collaborating.</p> + + <p><a href="https://donate.torproject.org">Donate</a> to help keep Tor fast, strong, and secure.</p> + + <div style="background-color: #7d4698; padding: 6px 8px 6px 8px; +-webkit-border-radius:3px; border-radius:3px; margin: 0 auto; width:200px; text-align: center;"><em><a href="https://donate.torproject.org" style="font-size: 24px; font-family: Source sans pro, Helvetica, Arial, sans-serif; font-weight: bold; color: #ffffff; text-decoration: none; display:inline-block;" target="_blank">DONATE</a></em></div> + </td> + </tr> + <tr> + <td style="padding:0 15px;"> + <p>The Tor Project is a US 501(c)(3) non-profit organization advancing human rights and freedoms by creating and deploying free and open-source anonymity and privacy technologies, supporting their unrestricted availability and use, and furthering their scientific and popular understanding.</p> + + <hr /> + <p><a href="https://facebook.com/torproject"><img alt="" src="https://blog.torproject.org/sites/default/files/inline-images/tor-facebook.…" style="width: 25px; height: 25px; margin: 3px;" /></a><a href="https://twitter.com/torproject"> <img alt="tor-twitter" src="https://blog.torproject.org/sites/default/files/inline-images/tor-twitter.p…" style="width: 25px; height: 25px; margin: 3px;" /></a><a href="https://instagram.com/torproject"> <img alt="tor-insta" src="https://blog.torproject.org/sites/default/files/inline-images/instagram-tor…" style="width: 25px; height: 25px; margin: 3px;" /></a></p> + + + </td> + </tr> + </tbody> + </table> + </td> + </tr> + </tbody> + </table> + </td> + </tr> + </tbody> + </table> + </td> + </tr> + </tbody> +</table> + +<table bgcolor="#ffffff" border="0" cellpadding="0" cellspacing="0" id="backgroundTable" st-sortable="left-image" width="100%"> + <tbody> + <tr> + <td> + <table align="center" border="0" cellpadding="0" cellspacing="0" class="devicewidth" width="650"> + <tbody> + <tr> + <td width="100%"> + <table align="center" bgcolor="#ffffff" border="0" cellpadding="0" cellspacing="0" class="devicewidth" width="650"> + <tbody> + <tr> + <td> </td> + </tr> + </tbody> + </table> + </td> + </tr> + </tbody> + </table> + </td> + </tr> + </tbody> +</table> diff --git a/content/archive/bug-smash-advocacy-what-we-are-reading-events/text/contents.lr b/content/archive/bug-smash-advocacy-what-we-are-reading-events/text/contents.lr new file mode 100644 index 0000000..63990c6 --- /dev/null +++ b/content/archive/bug-smash-advocacy-what-we-are-reading-events/text/contents.lr @@ -0,0 +1,128 @@ +_model: post +--- +_template: post.html +--- +author: steph(a)torproject.org +--- +pub_date: 2020-01-30 +--- +title: Bug Smash, Advocacy, What We're Reading, Events +--- +body: + +## Tor's Bug Smash Fund: Progress So Far ## + +https://blog.torproject.org/tor-bug-smash-fund-progress + +At the beginning of August 2019, we asked you to help us build our very first Bug Smash Fund. This fund will ensure that the Tor Project has a healthy reserve earmarked for maintenance work and smashing the bugs necessary to keep Tor Browser, the Tor network, and the many tools that rely on Tor strong, safe, and running smoothly. Together we raised $86,081. + +So far, we've marked 77 tickets with BugSmashFund. As of today, 56 of those tickets have been closed, and 21 of them are still in progress. With this reserve, we've been able to fix bugs and complete necessary maintenance on core tor, bridgedb, Snowflake, and Metrics, as well as complete the Tor Browser ESR 68 migration. Roughly half of the Bug Smash Fund remains available for allocation, and we will continue to tag relevant maintenance work and bug fixing tickets that will be covered with this reserve. Thank you for supporting this work. Find out what tickets we've closed so far: https://blog.torproject.org/tor-bug-smash-fund-progress + +## Help Stop the Sale of Public Interest Registry to a Private Equity Firm ## + +https://act.eff.org/action/help-stop-the-sale-of-public-interest-registry-to-a-private-equity-firm + +Last month it was suddenly announced that the nonprofit that owns the .ORG domain registry was planning to sell it to a private equity firm, Ethos Capital. This could impact the millions of individuals and organizations that have a .ORG website, including the Tor Project, subjecting them to potential censorship and leaving the door open for price increases on domain registration and renewals. + +Please take action today and add your name to the twenty-thousand individuals who have opposed the sale. + +## Buying a smart phone on the cheap? Privacy might be the price you have to pay ## + +https://privacyinternational.org/advocacy/3320/open-letter-google + +https://privacyintyqcroe.onion/advocacy/3320/open-letter-google + +Research by Privacy International shows that cheap smartphones come with a hidden cost: pre-installed apps that can't be deleted and that leak your data. + +We're telling Google it's time to take action on pre-installed apps. Add your voice here: https://privacyinternational.org/petition. + +## Privacy isn't about having something to hide. ## + +We believe technology must be designed in an ethical way that respects people's digital rights. Privacy cannot be an afterthought with room for interpretation by businesses that thrive on exploiting us online. Privacy must be the default. + +https://www.nytimes.com/2019/12/29/technology/california-privacy-law.html + +https://www.nytimes3xbfgragh.onion/2019/12/29/technology/california-privacy-law.html + +## New Releases ## + +Tor 0.4.3.1-alpha + +https://blog.torproject.org/new-alpha-release-tor-0431-alpha + +This is the first alpha release in the 0.4.3.x series. It includes improved support for application integration of onion services, support for building in a client-only mode, and newly improved internal documentation (online at https://src-ref.docs.torproject.org/tor/) It also has numerous other small bugfixes and features, as well as improvements to our code's internal organization that should help us write better code in the future. + +Tor Browser 9.5a4 + +https://blog.torproject.org/new-release-tor-browser-95a4 + +This new alpha release picks up security fixes for Firefox 68.4.0esr and 68.4.1esr. In addition, this release updates the bundled NoScript extension to its latest version. + +Tor Browser 9.0.3 & 9.0.4 + +https://blog.torproject.org/new-release-tor-browser-903 + +https://blog.torproject.org/new-release-tor-browser-904 + +9.0.4 fixes a critical security issue in Firefox: CVE-2019-17026. + +9.0.3 picks up security fixes for Firefox 68.4.0esr. We also updated Tor to 0.4.2.5 for the desktop versions. On Android we fixed a possible crash after the bootstrap. + +Stem 1.8 + +https://blog.torproject.org/new-release-stem-18 + +Stem is a Python library for interacting with Tor. With it you can script against your relay, descriptor data, or even write applications like Nyx. + +## What We're Reading ## + +"Reporters Face New Threats From the Governments They Cover," James Risen, The New York Times. [.onion] + +https://nytimes3xbfgragh.onion/2020/01/26/opinion/greenwald-brazil-reporter.html + +https://nytimes.com/2020/01/26/opinion/greenwald-brazil-reporter.html + +"Both the Trump administration and the right-wing Brazilian government of President Jair Bolsonaro seem to have decided to experiment with such draconian anti-press tactics..." + +"The Trump Administration's Lies About Encryption Are Putting Our Privacy in Danger," Trevor Timm. + +http://gen.medium.com/the-trump-administrations-lies-about-encryption-are-putting-our-privacy-in-danger-1291d5582283 + +"The Trump administration is now engaged in a multipronged effort to pressure tech companies to weaken encryption protecting the privacy of billions of people. And make no mistake: They are blatantly lying about it to try to get their way." + +"You Are Now Remotely Controlled," Shoshana Zuboff, The New York Times. + +https://www.nytimes3xbfgragh.onion/2020/01/24/opinion/sunday/surveillance-capitalism.html + +https://nytimes.com/2020/01/24/opinion/sunday/surveillance-capitalism.html + +"Surveillance capitalists exploit the widening inequity of knowledge for the sake of profits. They manipulate the economy, our society and even our lives with impunity, endangering not just individual privacy but democracy itself." + + +## Upcoming Events with Tor ## + +FOSDEM. Belgium, Brussels. 1-2 February 2020. https://blog.torproject.org/tor-fosdem-2020-brussels + +FOSDEM's Interview with Pili, Tor Project, Project Manager: https://fosdem.org/2020/interviews/pili-guerra/ + +## Join Our Community ## + +Getting involved with Tor is easy. Run a relay to make the network faster and more decentralized: https://trac.torproject.org/projects/tor/wiki/TorRelayGuide + +Run a bridge to help censored users access Tor: https://blog.torproject.org/run-tor-bridges-defend-open-internet + +Learn about each of our teams and start collaborating: https://trac.torproject.org/projects/tor/wiki/WikiStart#Teams + +Donate to help keep Tor fast, strong, and secure. https://donate.torproject.org + +-- + +The Tor Project is a US 501(c)(3) non-profit organization advancing human rights and freedoms by creating and deploying free and open-source anonymity and privacy technologies, supporting their unrestricted availability and use, and furthering their scientific and popular understanding. + +Twitter: https://twitter.com/torproject + +Facebook: https://facebook.com/torproject + +Instagram: https://instagram.com/torproject + +Mastodon: http://mastodon.social/@torproject

1 0