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

[tor/release-0.4.5] relay: Add bloomfiter of relay address + {OR|Dir}Port
by dgoulet＠torproject.org 29 Jan '21

29 Jan '21

commit 8dda7bfdb84a5e4b3b422592f811a465e37bb155 Author: David Goulet <dgoulet(a)torproject.org> Date: Wed Jan 27 21:49:56 2021 -0500 relay: Add bloomfiter of relay address + {OR|Dir}Port In order to deny re-entry in the network, we now keep a bloomfilter of relay ORPort + address and authorities ORPort + address and DirPort + address combinations. So when an Exit stream is handled, we deny anything connecting back into the network on the ORPorts for relays and on the ORPort+DirPort for the authorities. Related to #2667 Signed-off-by: David Goulet <dgoulet(a)torproject.org> --- src/core/or/address_set.c | 74 +++++++++++++++++++++++++++++++++++++++++ src/core/or/address_set.h | 18 +++++++++- src/feature/nodelist/dirlist.c | 9 +++-- src/feature/nodelist/nodelist.c | 64 +++++++++++++++++++++++++++++------ src/feature/nodelist/nodelist.h | 5 ++- 5 files changed, 154 insertions(+), 16 deletions(-) diff --git a/src/core/or/address_set.c b/src/core/or/address_set.c index d618ffc3d6..fcddc55e9f 100644 --- a/src/core/or/address_set.c +++ b/src/core/or/address_set.c @@ -69,3 +69,77 @@ address_set_probably_contains(const address_set_t *set, { return bloomfilt_probably_contains(set, addr); } + +/* Length of the item is an address (IPv4 or IPv6) and a 2 byte port. We use + * 16 bytes for the address here (IPv6) since we do not know which family + * the given address in the item thus in the case of IPv4, the extra bytes + * are simply zeroes to accomodate. */ +#define BLOOMFILT_ADDR_PORT_ITEM_LEN (16 + sizeof(uint16_t)) + +/** Build an item for the bloomfilter consisting of an address and port pair. + * + * If the given address is _not_ AF_INET or AF_INET6, then the item is an + * array of 0s. + * + * Return a pointer to a static buffer containing the item. Next call to this + * function invalidates its previous content. */ +static const uint8_t * +build_addr_port_item(const tor_addr_t *addr, const uint16_t port) +{ + static uint8_t data[BLOOMFILT_ADDR_PORT_ITEM_LEN]; + + memset(data, 0, sizeof(data)); + switch (tor_addr_family(addr)) { + case AF_INET: + memcpy(data, &addr->addr.in_addr.s_addr, 4); + break; + case AF_INET6: + memcpy(data, &addr->addr.in6_addr.s6_addr, 16); + break; + case AF_UNSPEC: + /* Leave the 0. */ + break; + default: + /* LCOV_EXCL_START */ + tor_fragile_assert(); + /* LCOV_EXCL_STOP */ + } + + memcpy(data + 16, &port, sizeof(port)); + return data; +} + +/** Return a hash value for the given item that the bloomfilter will use. */ +static uint64_t +bloomfilt_addr_port_hash(const struct sipkey *key, + const void *item) +{ + return siphash24(item, BLOOMFILT_ADDR_PORT_ITEM_LEN, key); +} + +/** Allocate and return an addr_port_set_t, suitable for holding up to + * max_address_guess distinct values. */ +addr_port_set_t * +addr_port_set_new(int max_addresses_guess) +{ + uint8_t k[BLOOMFILT_KEY_LEN]; + crypto_rand((void*)k, sizeof(k)); + return bloomfilt_new(max_addresses_guess, bloomfilt_addr_port_hash, k); +} + +/** Add an address and port pair to the given set. */ +void +addr_port_set_add(addr_port_set_t *set, const tor_addr_t *addr, uint16_t port) +{ + bloomfilt_add(set, build_addr_port_item(addr, port)); +} + +/** Return true if the given address and port pair are in the set. Of course, + * this is a bloomfilter and thus in rare occasion, a false positive happens + * thus the "probably". */ +bool +addr_port_set_probably_contains(const addr_port_set_t *set, + const tor_addr_t *addr, uint16_t port) +{ + return !!bloomfilt_probably_contains(set, build_addr_port_item(addr, port)); +} diff --git a/src/core/or/address_set.h b/src/core/or/address_set.h index 33887a7c9e..2c78ab0576 100644 --- a/src/core/or/address_set.h +++ b/src/core/or/address_set.h @@ -13,13 +13,14 @@ #include "lib/cc/torint.h" #include "lib/container/bloomfilt.h" +struct tor_addr_t; + /** * An address_set_t represents a set of tor_addr_t values. The implementation * is probabilistic: false negatives cannot occur but false positives are * possible. */ typedef struct bloomfilt_t address_set_t; -struct tor_addr_t; address_set_t *address_set_new(int max_addresses_guess); #define address_set_free(set) bloomfilt_free(set) @@ -28,4 +29,19 @@ void address_set_add_ipv4h(address_set_t *set, uint32_t addr); int address_set_probably_contains(const address_set_t *set, const struct tor_addr_t *addr); +/** + * An addr_port_set_t represents a set of tor_addr_t values with a uint16_t + * port value. The implementation is probabilistic: false negatives cannot + * occur but false positives are possible. + */ +typedef struct bloomfilt_t addr_port_set_t; + +addr_port_set_t *addr_port_set_new(int max_addresses_guess); +#define addr_port_set_free(s) bloomfilt_free(s) +void addr_port_set_add(addr_port_set_t *set, + const struct tor_addr_t *addr, uint16_t port); +bool addr_port_set_probably_contains(const addr_port_set_t *set, + const struct tor_addr_t *addr, + uint16_t port); + #endif /* !defined(TOR_ADDRESS_SET_H) */ diff --git a/src/feature/nodelist/dirlist.c b/src/feature/nodelist/dirlist.c index 576a6a2e49..423c4106e2 100644 --- a/src/feature/nodelist/dirlist.c +++ b/src/feature/nodelist/dirlist.c @@ -58,10 +58,13 @@ add_trusted_dir_to_nodelist_addr_set(const dir_server_t *dir) tor_assert(dir); tor_assert(dir->is_authority); - /* Add IPv4 and then IPv6 if applicable. */ - nodelist_add_addr_to_address_set(&dir->ipv4_addr); + /* Add IPv4 and then IPv6 if applicable. For authorities, we add the ORPort + * and DirPort so re-entry into the network back to them is not possible. */ + nodelist_add_addr_to_address_set(&dir->ipv4_addr, dir->ipv4_orport, + dir->ipv4_dirport); if (!tor_addr_is_null(&dir->ipv6_addr)) { - nodelist_add_addr_to_address_set(&dir->ipv6_addr); + /* IPv6 DirPort is not a thing yet for authorities. */ + nodelist_add_addr_to_address_set(&dir->ipv6_addr, dir->ipv6_orport, 0); } } diff --git a/src/feature/nodelist/nodelist.c b/src/feature/nodelist/nodelist.c index cfa8b69f81..0c9bdb3c0e 100644 --- a/src/feature/nodelist/nodelist.c +++ b/src/feature/nodelist/nodelist.c @@ -135,6 +135,10 @@ typedef struct nodelist_t { /* Set of addresses that belong to nodes we believe in. */ address_set_t *node_addrs; + /* Set of addresses + port that belong to nodes we know and that we don't + * allow network re-entry towards them. */ + addr_port_set_t *reentry_set; + /* The valid-after time of the last live consensus that initialized the * nodelist. We use this to detect outdated nodelists that need to be * rebuilt using a newer consensus. */ @@ -447,40 +451,58 @@ node_addrs_changed(node_t *node) static void node_add_to_address_set(const node_t *node) { - if (!the_nodelist || !the_nodelist->node_addrs) + if (!the_nodelist || + !the_nodelist->node_addrs || !the_nodelist->reentry_set) return; - /* These various address sources can be redundant, but it's likely faster - * to add them all than to compare them all for equality. */ + /* These various address sources can be redundant, but it's likely faster to + * add them all than to compare them all for equality. + * + * For relays, we only add the ORPort in the addr+port set since we want to + * allow re-entry into the network to the DirPort so the self reachability + * test succeeds and thus the 0 value for the DirPort. */ if (node->rs) { if (!tor_addr_is_null(&node->rs->ipv4_addr)) - nodelist_add_addr_to_address_set(&node->rs->ipv4_addr); + nodelist_add_addr_to_address_set(&node->rs->ipv4_addr, + node->rs->ipv4_orport, 0); if (!tor_addr_is_null(&node->rs->ipv6_addr)) - nodelist_add_addr_to_address_set(&node->rs->ipv6_addr); + nodelist_add_addr_to_address_set(&node->rs->ipv6_addr, + node->rs->ipv6_orport, 0); } if (node->ri) { if (!tor_addr_is_null(&node->ri->ipv4_addr)) - nodelist_add_addr_to_address_set(&node->ri->ipv4_addr); + nodelist_add_addr_to_address_set(&node->ri->ipv4_addr, + node->ri->ipv4_orport, 0); if (!tor_addr_is_null(&node->ri->ipv6_addr)) - nodelist_add_addr_to_address_set(&node->ri->ipv6_addr); + nodelist_add_addr_to_address_set(&node->ri->ipv6_addr, + node->ri->ipv6_orport, 0); } if (node->md) { if (!tor_addr_is_null(&node->md->ipv6_addr)) - nodelist_add_addr_to_address_set(&node->md->ipv6_addr); + nodelist_add_addr_to_address_set(&node->md->ipv6_addr, + node->md->ipv6_orport, 0); } } /** Add the given address into the nodelist address set. */ void -nodelist_add_addr_to_address_set(const tor_addr_t *addr) +nodelist_add_addr_to_address_set(const tor_addr_t *addr, + uint16_t or_port, uint16_t dir_port) { if (BUG(!addr) || tor_addr_is_null(addr) || (!tor_addr_is_v4(addr) && !tor_addr_is_v6(addr)) || - !the_nodelist || !the_nodelist->node_addrs) { + !the_nodelist || !the_nodelist->node_addrs || + !the_nodelist->reentry_set) { return; } address_set_add(the_nodelist->node_addrs, addr); + if (or_port != 0) { + addr_port_set_add(the_nodelist->reentry_set, addr, or_port); + } + if (dir_port != 0) { + addr_port_set_add(the_nodelist->reentry_set, addr, dir_port); + } } /** Return true if <b>addr</b> is the address of some node in the nodelist. @@ -497,6 +519,21 @@ nodelist_probably_contains_address(const tor_addr_t *addr) return address_set_probably_contains(the_nodelist->node_addrs, addr); } +/** Return true if <b>addr</b> is the address of some node in the nodelist and + * corresponds also to the given port. If not, probably return false. */ +bool +nodelist_reentry_probably_contains(const tor_addr_t *addr, uint16_t port) +{ + if (BUG(!addr) || BUG(!port)) + return false; + + if (!the_nodelist || !the_nodelist->reentry_set) + return false; + + return addr_port_set_probably_contains(the_nodelist->reentry_set, + addr, port); +} + /** Add <b>ri</b> to an appropriate node in the nodelist. If we replace an * old routerinfo, and <b>ri_old_out</b> is not NULL, set *<b>ri_old_out</b> * to the previous routerinfo. @@ -628,10 +665,13 @@ nodelist_set_consensus(const networkstatus_t *ns) * v6). Then we add the number of configured trusted authorities we have. */ int estimated_addresses = smartlist_len(ns->routerstatus_list) * get_estimated_address_per_node(); - estimated_addresses += (get_n_authorities(V3_DIRINFO & BRIDGE_DIRINFO) * + estimated_addresses += (get_n_authorities(V3_DIRINFO | BRIDGE_DIRINFO) * get_estimated_address_per_node()); address_set_free(the_nodelist->node_addrs); + addr_port_set_free(the_nodelist->reentry_set); the_nodelist->node_addrs = address_set_new(estimated_addresses); + /* Times two here is for both the ORPort and DirPort. */ + the_nodelist->reentry_set = addr_port_set_new(estimated_addresses * 2); SMARTLIST_FOREACH_BEGIN(ns->routerstatus_list, routerstatus_t *, rs) { node_t *node = node_get_or_create(rs->identity_digest); @@ -858,6 +898,8 @@ nodelist_free_all(void) address_set_free(the_nodelist->node_addrs); the_nodelist->node_addrs = NULL; + addr_port_set_free(the_nodelist->reentry_set); + the_nodelist->reentry_set = NULL; tor_free(the_nodelist); } diff --git a/src/feature/nodelist/nodelist.h b/src/feature/nodelist/nodelist.h index b762fb339c..ada0a640a1 100644 --- a/src/feature/nodelist/nodelist.h +++ b/src/feature/nodelist/nodelist.h @@ -35,7 +35,10 @@ node_t *nodelist_add_microdesc(microdesc_t *md); void nodelist_set_consensus(const networkstatus_t *ns); void nodelist_ensure_freshness(const networkstatus_t *ns); int nodelist_probably_contains_address(const tor_addr_t *addr); -void nodelist_add_addr_to_address_set(const tor_addr_t *addr); +bool nodelist_reentry_probably_contains(const tor_addr_t *addr, + uint16_t port); +void nodelist_add_addr_to_address_set(const tor_addr_t *addr, + uint16_t or_port, uint16_t dir_port); void nodelist_remove_microdesc(const char *identity_digest, microdesc_t *md); void nodelist_remove_routerinfo(routerinfo_t *ri);

1 0

[tor/release-0.4.5] test: Add test for exits blocking reentry to the network
by dgoulet＠torproject.org 29 Jan '21

29 Jan '21

commit 46efbcb116b70f417c9e4241e4480688169b1813 Author: George Kadianakis <desnacked(a)riseup.net> Date: Fri Jan 29 18:21:30 2021 +0200 test: Add test for exits blocking reentry to the network Signed-off-by: David Goulet <dgoulet(a)torproject.org> --- src/test/test_address_set.c | 80 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 80 insertions(+) diff --git a/src/test/test_address_set.c b/src/test/test_address_set.c index 3fee322c47..55a0b106d2 100644 --- a/src/test/test_address_set.c +++ b/src/test/test_address_set.c @@ -181,11 +181,91 @@ test_nodelist(void *arg) UNMOCK(dirlist_add_trusted_dir_addresses); } +/** Test that the no-reentry exit filter works as intended */ +static void +test_exit_no_reentry(void *arg) +{ + routerstatus_t *rs = NULL; microdesc_t *md = NULL; routerinfo_t *ri = NULL; + (void) arg; + + MOCK(networkstatus_get_latest_consensus, + mock_networkstatus_get_latest_consensus); + MOCK(networkstatus_get_latest_consensus_by_flavor, + mock_networkstatus_get_latest_consensus_by_flavor); + MOCK(get_estimated_address_per_node, + mock_get_estimated_address_per_node); + MOCK(dirlist_add_trusted_dir_addresses, + mock_dirlist_add_trusted_dir_addresses); + + dummy_ns = tor_malloc_zero(sizeof(*dummy_ns)); + dummy_ns->flavor = FLAV_MICRODESC; + dummy_ns->routerstatus_list = smartlist_new(); + + tor_addr_t addr_v4, addr_v6, dummy_addr; + tor_addr_parse(&addr_v4, "42.42.42.42"); + tor_addr_parse(&addr_v6, "1:2:3:4::"); + memset(&dummy_addr, 'A', sizeof(dummy_addr)); + + /* This will make the nodelist bloom filter very large + * (the_nodelist->node_addrs) so we will fail the contain test rarely. */ + addr_per_node = 1024; + + /* After this point the nodelist is populated with the directory authorities + * address and ports */ + nodelist_set_consensus(dummy_ns); + + /* The address set is empty. Try it anyway */ + tt_assert(!nodelist_reentry_probably_contains(&addr_v4, 244)); + tt_assert(!nodelist_reentry_probably_contains(&addr_v6, 244)); + + /* Now let's populate the network */ + md = tor_malloc_zero(sizeof(*md)); + ri = tor_malloc_zero(sizeof(*ri)); + rs = tor_malloc_zero(sizeof(*rs)); + crypto_rand(rs->identity_digest, sizeof(rs->identity_digest)); + crypto_rand(md->digest, sizeof(md->digest)); + memcpy(rs->descriptor_digest, md->digest, DIGEST256_LEN); + + /* Setup the rs, ri and md addresses. */ + tor_addr_copy(&rs->ipv4_addr, &addr_v4); + rs->ipv4_orport = 444; + tor_addr_parse(&rs->ipv6_addr, "1:2:3:4::"); + rs->ipv6_orport = 666; + tor_addr_copy(&ri->ipv4_addr, &addr_v4); + tor_addr_parse(&ri->ipv6_addr, "1:2:3:4::"); + tor_addr_parse(&md->ipv6_addr, "1:2:3:4::"); + + /* Add the rs to the consensus becoming a node_t. */ + smartlist_add(dummy_ns->routerstatus_list, rs); + nodelist_set_consensus(dummy_ns); + + /* Now that the nodelist is populated let's do some retry attempts */ + + /* First let's try an address that is on the no-reentry list, but with a + different port */ + tt_assert(!nodelist_reentry_probably_contains(&addr_v4, 666)); + tt_assert(!nodelist_reentry_probably_contains(&addr_v6, 444)); + + /* OK now let's try with the right address and right port */ + tt_assert(nodelist_reentry_probably_contains(&addr_v4, 444)); + tt_assert(nodelist_reentry_probably_contains(&addr_v6, 666)); + + done: + routerstatus_free(rs); routerinfo_free(ri); microdesc_free(md); + smartlist_clear(dummy_ns->routerstatus_list); + networkstatus_vote_free(dummy_ns); + UNMOCK(networkstatus_get_latest_consensus); + UNMOCK(networkstatus_get_latest_consensus_by_flavor); + UNMOCK(get_estimated_address_per_node); + UNMOCK(dirlist_add_trusted_dir_addresses); +} + struct testcase_t address_set_tests[] = { { "contains", test_contains, TT_FORK, NULL, NULL }, { "nodelist", test_nodelist, TT_FORK, NULL, NULL }, + { "exit_no_reentry", test_exit_no_reentry, TT_FORK, NULL, NULL }, END_OF_TESTCASES };

1 0

[tor/release-0.4.5] Merge branch 'maint-0.4.5' into release-0.4.5
by dgoulet＠torproject.org 29 Jan '21

29 Jan '21

commit 04d7007609c0a34cac8a15ffee4d528d669fdc10 Merge: dddc6a4b30 46efbcb116 Author: David Goulet <dgoulet(a)torproject.org> Date: Fri Jan 29 14:40:56 2021 -0500 Merge branch 'maint-0.4.5' into release-0.4.5 changes/ticket2667 | 4 +++ src/core/or/address_set.c | 74 ++++++++++++++++++++++++++++++++++++++ src/core/or/address_set.h | 18 +++++++++- src/core/or/connection_edge.c | 24 +++++++++++++ src/feature/nodelist/dirlist.c | 9 +++-- src/feature/nodelist/nodelist.c | 64 +++++++++++++++++++++++++++------ src/feature/nodelist/nodelist.h | 5 ++- src/test/test_address_set.c | 80 +++++++++++++++++++++++++++++++++++++++++ 8 files changed, 262 insertions(+), 16 deletions(-)

1 0

[translation/tails-onioncircuits_release] https://gitweb.torproject.org/translation.git/commit/?h=tails-onioncircuits_release
by translation＠torproject.org 29 Jan '21

29 Jan '21

commit f07f784c714200f5f45ce2660ffe66f755e56d94 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Jan 29 18:47:06 2021 +0000 https://gitweb.torproject.org/translation.git/commit/?h=tails-onioncircuits… --- pt_BR/onioncircuits.po | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pt_BR/onioncircuits.po b/pt_BR/onioncircuits.po index f22fa05b85..1d025ebe37 100644 --- a/pt_BR/onioncircuits.po +++ b/pt_BR/onioncircuits.po @@ -5,7 +5,7 @@ # Translators: # Communia <ameaneantie(a)riseup.net>, 2016-2018 # Maicon Grahl <maicongrahl(a)hotmail.com>, 2016 -# Rodrigo, 2016 +# rhcastilhos, 2016 # yyyyyyyan <contact(a)yyyyyyyan.tech>, 2020 msgid "" msgstr ""

1 0

[lego/master] Fix tor-icons.woff url in bootstrap.css
by hiro＠torproject.org 29 Jan '21

29 Jan '21

commit 3361e2595ed5fee8f9c44a0e43da78057ef3387d Author: Duncan <duncan(a)torproject.org> Date: Wed Jan 20 16:16:31 2021 +0000 Fix tor-icons.woff url in bootstrap.css --- assets/static/css/bootstrap.css | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/assets/static/css/bootstrap.css b/assets/static/css/bootstrap.css index 39852d5..5efb48f 100644 --- a/assets/static/css/bootstrap.css +++ b/assets/static/css/bootstrap.css @@ -7403,7 +7403,7 @@ main { src: url("fonts/SourceCodePro/SourceCodePro-Regular.ttf"); } @font-face { font-family: Tor Icons; - src: url("fonts/TorIcons/tor-icons.eot?#iefix") format("embedded-opentype"), url("fonts/TorIcons/tor-icons.woff2") format("woff2"), url("fonsts/TorIcons/tor-icons.woff") format("woff"), url("fonts/TorIcons/tor-icons.ttf") format("truetype"), url("fonts/TorIcons/tor-icons.svg?#tor-icons") format("svg"); } + src: url("fonts/TorIcons/tor-icons.eot?#iefix") format("embedded-opentype"), url("fonts/TorIcons/tor-icons.woff2") format("woff2"), url("fonts/TorIcons/tor-icons.woff") format("woff"), url("fonts/TorIcons/tor-icons.ttf") format("truetype"), url("fonts/TorIcons/tor-icons.svg?#tor-icons") format("svg"); } .ti:before { font-family: Tor Icons !important; font-style: normal;

1 0

[newsletter/master] Add January newsletter
by hiro＠torproject.org 29 Jan '21

29 Jan '21

commit be23366c8d4521e60eafc8dc246854d35c3e171c Author: hiro <hiro(a)torproject.org> Date: Fri Jan 29 18:37:33 2021 +0100 Add January newsletter --- .../2020-fundraising-results-thank-you/contents.lr | 167 +++++++++++++++++++++ .../text/contents.lr | 111 ++++++++++++++ 2 files changed, 278 insertions(+) diff --git a/content/archive/2020-fundraising-results-thank-you/contents.lr b/content/archive/2020-fundraising-results-thank-you/contents.lr new file mode 100644 index 0000000..8bbcd4c --- /dev/null +++ b/content/archive/2020-fundraising-results-thank-you/contents.lr @@ -0,0 +1,167 @@ +_model: post +--- +_template: newsletter.html +--- +author: smith(a)torproject.org +--- +pub_date: 2020-01-29 +--- +title: 2020 Fundraising Results: Thank You! +--- +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="680"> + <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" bgcolor="#ffffff" border="0" cellpadding="0" cellspacing="0" class="devicewidth" width="650"> + <tbody> + <tr> + <td style="padding:0 15px 15px 15px;"> + <hr /> + <h1><a href="https://blog.torproject.org/use-a-mask-use-tor-thank-you">2020 Fundraising Results: Thank You!</a></h1> + + <p><a href="https://blog.torproject.org/use-a-mask-use-tor-thank-you"><img alt="" src="https://blog.torproject.org/sites/default/files/styles/full_width/public/im…" style="width: 640px; height: 320px;" /></a></p> + + <div class="field field--name-body field--type-text-with-summary field--label-hidden field--item" property="schema:text"> + <p>We are pleased to announce that in 2020, despite the cancellations of in-person events and the sharp decrease in individual donations we saw at the beginning of the pandemic, you helped us to raise $913,110 from individuals, more than any calendar year in the Tor Project’s history. You contributed $376,315 of this figure during the end-of-year campaign—this includes the generous $100,000 match by the <a href="https://blog.torproject.org/friends-of-tor-match-2020">Friends of Tor</a>. (That’s a 19% increase over last year’s year-end campaign.)</p> + + <p><strong>Thank you to everyone who made a donation in 2020! </strong>You make it possible to resist the surveillance pandemic. You’ve made it possible for the Tor Project and the tools we support to survive a very difficult time, and to <a href="https://blog.torproject.org/tor-in-2021">prepare for 2021 with ambitious plans</a>.</p> + + <p><a href="https://blog.torproject.org/use-a-mask-use-tor-thank-you#comment-form">Vist the blog for more details about the details of Tor's fundraising in 2020, and what we have prepared for 2021</a>.</p> + </div> + + <hr /> + <h1><a href="https://blog.torproject.org/state-of-ipv6-support-tor-network"><span class="quickedit-field" data-quickedit-field-id="node/1971/title/en/full" property="schema:name">The state of IPv6 support on the Tor network</span></a></h1> + + <p><a href="https://blog.torproject.org/state-of-ipv6-support-tor-network"><img alt="" src="https://blog.torproject.org/sites/default/files/inline-images/versions.png" style="width: 640px; height: 400px;" /></a></p> + + <footer> + <p>In <a href="https://labs.ripe.net/Members/tor_grants/a-look-into-the-tor-network-work-o…">our last article</a>, published in <a href="https://labs.ripe.net/Members/tor_grants/a-look-into-the-tor-network-work-o…">RIPE's website</a>, we described the work that happened in 2020 related to giving <a href="https://blog.torproject.org/ipv6-future-i-hear">IPv6 support</a> to the Tor network.</p> + </footer> + + <div class="node__content"> + <div class="field field--name-body field--type-text-with-summary field--label-hidden field--item quickedit-field" data-quickedit-field-id="node/1971/body/en/full" property="schema:text"> + <p style="line-height:1.38"><a href="https://blog.torproject.org/node/1949">Tor 0.4.5.1-alpha</a> is the first release that includes all the work described in the RIPE article. Relays running 0.4.5.1-alpha are the first to report IPv6 bandwidth statistics.</p> + + <p style="line-height:1.38">As of December 2, 2020, 54% of the relays on the network run a version of Tor that supports IPv6. Of the 6852 relays in the network, 3587 are running <a href="https://metrics.torproject.org/versions.html">version 0.4.4 </a>and 8 relays are running the <a href="https://blog.torproject.org/node/1958">latest Tor version 0.4.5</a>. From all those, 1588 are announcing an IPv6 address and port for the OR protocol. 1587 relays are reachable on IPv6 by the directory authorities. 626 permit exiting to <a href="https://metrics.torproject.org/relays-ipv6.html">IPv6 targets</a>.</p> + + <p style="line-height:1.38">Read more about <a href="https://blog.torproject.org/state-of-ipv6-support-tor-network">the state of IPv6 on the Tor network on our blog</a>.</p> + </div> + </div> + + <hr /> + <h1 class="title"><a href="https://blog.torproject.org/in-memoriam-of-karsten-loesing">In memoriam of Karsten Loesing </a></h1> + + <p><a href="https://blog.torproject.org/in-memoriam-of-karsten-loesing"><img alt="" src="https://blog.torproject.org/sites/default/files/styles/full_width/public/im…" style="width: 640px; height: 426px;" /></a></p> + + <p><em>Image credit: uni-bamberg.de press office</em>, <a href="https://www.uni-bamberg.de/forschung/profil/kulturgut/dossier/artikel/kein-…">Kein Häuten der Zwiebel</a> (2007).</p> + + <p class="ace-line">It's with deep sorrow that we share that our dear friend, colleague, and Tor core contributor <a href="https://blog.torproject.org/in-memoriam-of-karsten-loesing">Karsten Loesing</a> passed away on the afternoon of Friday, December 18, 2020. No one is prepared for such an unimaginable loss. Our deepest sympathies go to Karsten's family at this moment, his wife and his children.</p> + + <p>We all loved him and his contribution to the Tor Project will always be remembered from the depth of our hearts. We will be dedicating our next release of core tor to Karsten's memory. </p> + + <p>Rest in peace, Karsten.</p> + + <hr /> + <h1>New Releases</h1> + + <h2 class="title"><a href="https://blog.torproject.org/new-release-tor-browser-1009"><span class="quickedit-field" data-quickedit-field-id="node/1988/title/en/teaser" property="schema:name">Tor Browser 10.0.9</span> </a></h2> + + <p>This release updates Firefox to 78.7.0esr for desktop and Firefox for Android to 85.1.0. This release includes important security updates to Firefox for Desktop, and similar important security updates to Firefox for Android. <a href="https://blog.torproject.org/new-release-tor-browser-1009">Full changelog.</a></p> + + <h2 class="title"><a href="https://blog.torproject.org/new-release-tor-browser-105a8"><span class="quickedit-field" data-quickedit-field-id="node/1987/title/en/teaser" property="schema:name">Tor Browser 10.5a8</span></a><a href="https://blog.torproject.org/new-release-tor-browser-1007" rel="bookmark"> </a></h2> + + <p>This release updates Firefox to 78.7.0esr for desktop and Firefox for Android to 85.1.0. Additionally, we update Tor to 0.4.5.4-rc. This release includes important security updates to Firefox for Desktop, and similar important security updates to Firefox for Android. <a href="https://blog.torproject.org/new-release-tor-browser-105a8">Full changelog</a><a href="https://blog.torproject.org/new-release-tor-browser-1007">.</a></p> + + <h2 class="title"><a href="https://blog.torproject.org/node/1973"><span class="quickedit-field" data-quickedit-field-id="node/1973/title/en/teaser" property="schema:name">Tor 0.4.5.4-rc</span> </a></h2> + + <p>Tor 0.4.5.4-rc is the second release candidate in its series. It fixes several bugs present in previous releases. We expect that the stable release will be the same, or almost the same, as this release candidate, unless serious bugs are found.<a href="https://blog.torproject.org/node/1973"> Full changelog</a>.</p> + + <h2 class="title"><a href="https://blog.torproject.org/new-release-tor-browser-105a7" rel="bookmark"><span class="quickedit-field" data-quickedit-field-id="node/1972/title/en/teaser" property="schema:name">Tor Browser 10.5a7</span></a></h2> + + <p>This release updates Firefox to 78.6.1esr for desktop and Firefox for Android to 85.0.0-beta.7. Additionally, we update Tor to 0.4.5.3-rc. This versions also fixes a crash seen by macOS users on the new M1 processor. <a href="https://blog.torproject.org/new-release-tor-browser-105a7">Full changelog</a>.</p> + + <h2 class="title"><a href="https://blog.torproject.org/new-release-tor-browser-1008" rel="bookmark"><span class="quickedit-field" data-quickedit-field-id="node/1970/title/en/teaser" property="schema:name">Tor Browser 10.0.8</span></a></h2> + + <p>This release updates Firefox for desktops to 78.6.1esr and Firefox for Android to 84.1.4. This version resolves instability on Apple macOS devices with the new M1 processor. <a href="https://blog.torproject.org/new-release-tor-browser-1008">Full changelog</a>.</p> + + <h2 class="title"><a href="https://blog.torproject.org/node/1969" rel="bookmark"><span class="quickedit-field" data-quickedit-field-id="node/1969/title/en/teaser" property="schema:name">Tor 0.4.5.3-rc</span></a></h2> + + <p>Tor 0.4.5.3-rc is the first release candidate in its series. It fixes several bugs, including one that broke onion services on certain older ARM CPUs, and another that made v3 onion services less reliable. <a href="https://blog.torproject.org/node/1969">Full changelog</a>.</p> + + <hr /> + <h1>Circumventing Social Media Censorship in Uganda</h1> + + <p><span class="css-901oao css-16my406 r-poiln3 r-bcqeeo r-qvutc0"><a href="https://news.trust.org/item/20210120134502-2jnhz/">A recent internet blackout and continuing social media censorship in Uganda</a> is an attempt by the government to keep citizens and the rest of the world in the dark during an election period. </span></p> + + <p><span class="css-901oao css-16my406 r-poiln3 r-bcqeeo r-qvutc0">Using Tor Browser will circumvent this censorship as connections to Tor are still working, but it appears that </span><a class="css-4rbku5 css-18t94o4 css-901oao css-16my406 r-1n1174f r-1loqt21 r-poiln3 r-bcqeeo r-qvutc0" data-focusable="true" dir="ltr" href="https://t.co/Bfvw4mqWAV?amp=1" rel=" noopener noreferrer" role="link" target="_blank"><span aria-hidden="true" class="css-901oao css-16my406 r-poiln3 r-hiw28u r-bcqeeo r-qvutc0">http://</span>torproject.org</a><span class="css-901oao css-16my406 r-poiln3 r-bcqeeo r-qvutc0"> is blocked. You'll need to use one of the following methods to download Tor Browser:</span></p> + + <p><span class="css-901oao css-16my406 r-poiln3 r-bcqeeo r-qvutc0">1. Use a trusted mirror (</span><a class="css-4rbku5 css-18t94o4 css-901oao css-16my406 r-1n1174f r-1loqt21 r-poiln3 r-bcqeeo r-qvutc0" data-focusable="true" dir="ltr" href="https://t.co/sReB4ACljW?amp=1" rel=" noopener noreferrer" role="link" target="_blank"><span aria-hidden="true" class="css-901oao css-16my406 r-poiln3 r-hiw28u r-bcqeeo r-qvutc0">https://</span>tor.ccc.de</a><span class="css-901oao css-16my406 r-poiln3 r-bcqeeo r-qvutc0">).</span></p> + + <p><span class="css-901oao css-16my406 r-poiln3 r-bcqeeo r-qvutc0">2. Email GetTor(a)torproject.org with your operating system and it will reply with Tor Browser files.</span></p> + + <p><span class="css-901oao css-16my406 r-poiln3 r-bcqeeo r-qvutc0">3. Download Tor Browser from<a href="https://guardianproject.info/fdroid/"> the Guardian Projects F-Droid repo</a>.</span></p> + + <hr /> + <h1>What We're Reading</h1> + + <p>"Tor Project’s crypto donations increased 23% in 2020," <a href="https://cointelegraph.com/news/tor-project-s-crypto-donations-increased-23-…">Coin Telegraph</a>.</p> + + <p>"Encryption is vital for attorney-client privilege in the digital era, and lawyers should fight for it," <a href="https://www.accessnow.org/encryption-attorney-client-privilege/">Access Now</a>.</p> + + <p>"100 hours in the dark: How an election internet blackout hit poor Ugandans," <span class="article-container"><a href="https://news.trust.org/item/20210120134502-2jnhz/">Thomson Reuters Foundation</a>.</span></p> + + <div> + <p data-qa="headline" id="main-content">"You watch TV. Your TV watches back," <a href="https://www.washingtonpost.com/technology/2019/09/18/you-watch-tv-your-tv-w…">The Washington Post</a>.</p> + + <div> + <p>"Leaked Location Data Shows Another Muslim Prayer App Tracking Users," <a href="https://www.vice.com/en/article/xgz4n3/muslim-app-location-data-salaat-first">VICE</a>.</p> + + <p>"DuckDuckGo surpasses 100 million daily search queries for the first time," <a href="https://www.zdnet.com/article/duckduckgo-surpasses-100-million-daily-search…">ZDNet</a>.</p> + </div> + </div> + + <hr /> + <h1>Join Our Community</h1> + + <p>Getting involved with Tor is easy. <a href="https://community.torproject.org/relay/">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> + + <p><small><a href="{action.unsubscribeUrl}">I no longer want to receive Tor News</a> | <a href="{action.optOutUrl}">Please remove this email address from all communications from the Tor Project</a><br /> + {domain.address}<br /> + <a href="https://torproject.org">torproject.org</a></small></p> + </td> + </tr> + </tbody> + </table> + </td> + </tr> + </tbody> + </table> + </td> + </tr> + </tbody> +</table> + diff --git a/content/archive/2020-fundraising-results-thank-you/text/contents.lr b/content/archive/2020-fundraising-results-thank-you/text/contents.lr new file mode 100644 index 0000000..698634f --- /dev/null +++ b/content/archive/2020-fundraising-results-thank-you/text/contents.lr @@ -0,0 +1,111 @@ +_model: post +--- +_template: post.html +--- +author: smith(a)torproject.org +--- +pub_date: 2020-01-29 +--- +title: 2020 Fundraising Results: Thank You! +--- +body: + +## 2020 Fundraising Results: Thank You! ## + +https://blog.torproject.org/use-a-mask-use-tor-thank-you + +We are pleased to announce that in 2020, despite the cancellations of in-person events and the sharp decrease in individual donations we saw at the beginning of the pandemic, you helped us to raise $913,110 from individuals, more than any calendar year in the Tor Project’s history. You contributed $376,315 of this figure during the end-of-year campaign—this includes the generous $100,000 match by the Friends of Tor. (That’s a 19% increase over last year’s year-end campaign.) + +Thank you to everyone who made a donation in 2020! You make it possible to resist the surveillance pandemic. You’ve made it possible for the Tor Project and the tools we support to survive a very difficult time, and to prepare for 2021 with ambitious plans. + +Vist the blog for more details about the details of Tor's fundraising in 2020, and what we have prepared for 2021: https://blog.torproject.org/use-a-mask-use-tor-thank-you + +## The state of IPv6 support on the Tor network ## + +https://blog.torproject.org/state-of-ipv6-support-tor-network + +In our last article, published in RIPE's website, (https://labs.ripe.net/Members/tor_grants/a-look-into-the-tor-network-work-o…) we described the work that happened in 2020 related to giving IPv6 support (https://blog.torproject.org/ipv6-future-i-hear) to the Tor network. + +Tor 0.4.5.1-alpha (https://blog.torproject.org/node/1949) is the first release that includes all the work described in the RIPE article. Relays running 0.4.5.1-alpha are the first to report IPv6 bandwidth statistics. + +As of December 2, 2020, 54% of the relays on the network run a version of Tor that supports IPv6. Of the 6852 relays in the network, 3587 are running version 0.4.4 (https://metrics.torproject.org/versions.html) and 8 relays are running the latest Tor version 0.4.5 (https://blog.torproject.org/node/1958) From all those, 1588 are announcing an IPv6 address and port for the OR protocol. 1587 relays are reachable on IPv6 by the directory authorities. 626 permit exiting to IPv6 targets (https://metrics.torproject.org/relays-ipv6.html) + +Read more about the state of IPv6 on the Tor network on our blog: https://blog.torproject.org/state-of-ipv6-support-tor-network + +## In memoriam of Karsten Loesing ## + +blog.torproject.org/in-memoriam-of-karsten-loesing + +It's with deep sorrow that we share that our dear friend, colleague, and Tor core contributor Karsten Loesing passed away on the afternoon of Friday, December 18, 2020. No one is prepared for such an unimaginable loss. Our deepest sympathies go to Karsten's family at this moment, his wife and his children. + +We all loved him and his contribution to the Tor Project will always be remembered from the depth of our hearts. We will be dedicating our next release of core tor to Karsten's memory. + +Rest in peace, Karsten. + +## New Releases ## + +Tor Browser 10.0.9 + +https://blog.torproject.org/new-release-tor-browser-1009 + +This release updates Firefox to 78.7.0esr for desktop and Firefox for Android to 85.1.0. This release includes important security updates to Firefox for Desktop, and similar important security updates to Firefox for Android. + +Tor Browser 10.5a8 + +https://blog.torproject.org/new-release-tor-browser-105a8 + +This release updates Firefox to 78.7.0esr for desktop and Firefox for Android to 85.1.0. Additionally, we update Tor to 0.4.5.4-rc. This release includes important security updates to Firefox for Desktop, and similar important security updates to Firefox for Android. + +Tor 0.4.5.4-rc + +https://blog.torproject.org/node/1973 + +Tor 0.4.5.4-rc is the second release candidate in its series. It fixes several bugs present in previous releases. We expect that the stable release will be the same, or almost the same, as this release candidate, unless serious bugs are found. + +Tor Browser 10.5a7 + +https://blog.torproject.org/new-release-tor-browser-105a7 + +This release updates Firefox to 78.6.1esr for desktop and Firefox for Android to 85.0.0-beta.7. Additionally, we update Tor to 0.4.5.3-rc. This versions also fixes a crash seen by macOS users on the new M1 processor. + +Tor Browser 10.0.8 + +https://blog.torproject.org/new-release-tor-browser-1008 + +This release updates Firefox for desktops to 78.6.1esr and Firefox for Android to 84.1.4. This version resolves instability on Apple macOS devices with the new M1 processor. + +Tor 0.4.5.3-rc + +https://blog.torproject.org/node/1969 + +Tor 0.4.5.3-rc is the first release candidate in its series. It fixes several bugs, including one that broke onion services on certain older ARM CPUs, and another that made v3 onion services less reliable. + +## Upcoming Events with Tor ## + +No upcoming events. + +## What We're Reading ## + +"Tor Project’s crypto donations increased 23% in 2020," Coin Telegraph. (https://cointelegraph.com/news/tor-project-s-crypto-donations-increased-23-…) + +"Encryption is vital for attorney-client privilege in the digital era, and lawyers should fight for it," Access Now. (https://www.accessnow.org/encryption-attorney-client-privilege/) + +"100 hours in the dark: How an election internet blackout hit poor Ugandans," Thomson Reuters Foundation. (https://news.trust.org/item/20210120134502-2jnhz/) + +"You watch TV. Your TV watches back," The Washington Post. (https://www.washingtonpost.com/technology/2019/09/18/you-watch-tv-your-tv-w…) + +"Leaked Location Data Shows Another Muslim Prayer App Tracking Users," VICE. (https://www.vice.com/en/article/xgz4n3/muslim-app-location-data-salaat-first) + +"DuckDuckGo surpasses 100 million daily search queries for the first + +-- + +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

[manual/master] Fix #39
by gus＠torproject.org 29 Jan '21

29 Jan '21

commit b20f06431df5e3c5fe6fefe0a7444127d4485da1 Author: championquizzer <championquizzer(a)gmail.com> Date: Fri Jan 29 16:47:26 2021 +0530 Fix #39 --- content/installation/contents.lr | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/content/installation/contents.lr b/content/installation/contents.lr index 732b241..80eef95 100644 --- a/content/installation/contents.lr +++ b/content/installation/contents.lr @@ -45,11 +45,14 @@ For GNU/Linux: 5. You'll need to tell your GNU/Linux that you want the ability to execute shell scripts from the graphical interface or the command line. Navigate to the newly extracted Tor Browser directory. Right click on `start-tor-browser.desktop`, open Properties or Preferences and change the permission to allow executing file as program. - On the terminal from inside the Tor Browser directory you may also execute `chmod +x start-tor-browser.desktop` to make the file executable. Double-click the icon to start up Tor Browser for the first time. + Double-click the icon to start up Tor Browser for the first time. + + **Note:** On Ubuntu and some other distros if you try to launch the start-tor-browser.desktop file a text file might open up. +To change this behavior and launch Tor Browser instead, follow this: Open "Files" (GNOME Files/Nautilus) → open Preferences → go to the 'Behavior' Tab → Select "Run them" or "Ask what to do" under "Executable Text Files". +If you choose the latter click on "Run" after launching the start-tor-browser.desktop file. 6. Alternatively, from inside the Tor Browser directory, you can also start from the command line by running: `./start-tor-browser.desktop` - See here on how to [update Tor Browser](https://tb-manual.torproject.org/updating/).

1 0

[community/master] Add fields to support listing successfully completed projects
by gus＠torproject.org 29 Jan '21

29 Jan '21

commit 0694e2b1cd353a51a02a346910c61b626da8334e Author: Pili Guerra <pili(a)piliguerra.com> Date: Thu Jan 28 17:25:27 2021 +0100 Add fields to support listing successfully completed projects --- models/project.ini | 8 ++++++-- templates/gsoc.html | 21 ++++++++++++--------- 2 files changed, 18 insertions(+), 11 deletions(-) diff --git a/models/project.ini b/models/project.ini index 6d5f780..0590259 100644 --- a/models/project.ini +++ b/models/project.ini @@ -6,14 +6,18 @@ label = {{ this.title }} label = Title type = string -[fields.link] -label = Link +[fields.url] +label = url type = url [fields.active] label = Active type = boolean +[fields.completed] +label = Completed +type = boolean + [fields.subtitle] label = Subtitle type = markdown diff --git a/templates/gsoc.html b/templates/gsoc.html index 15f388d..115f666 100644 --- a/templates/gsoc.html +++ b/templates/gsoc.html @@ -7,18 +7,21 @@ <div class="col-12"> {% from "macros/projects.html" import render_active %} {% for child in this.children.filter(F.active == True).all() %} - <div class="row"> - {{ render_active(child, this.alt) }} - </div> - {% endfor %} - </div> - <div class="row"> - <ul> - {% for child in this.children.filter(F.active == False).all() %} - <li>{{ item.title }}</li> + <div class="row"> + {{ render_active(child, this.alt) }} + </div> {% endfor %} </div> <div class="row py-5 text-center mx-auto"> <p class="text-center">{{ _('None of these ideas seem appealing? You may also want to propose your own project idea — which often results in the best projects.') }} <a href="mailto:gso@torproject.org">{{ _('We invite you to contact us to discuss your own project idea.') }}</a></p> </div> + <div class="row"> + <h2>Past Projects</h2> + <p class="text-center">{{ _('Here are some successful projects which have been implemented in the past by Google Summer of Code and Outreachy participants') }}</p> + <ul> + {% for child in this.children.filter(F.active == False).filter(F.completed == True).all() %} + <li><a href={{ child.url }}>{{ child.title }}</a></li> + {% endfor %} + </ul> + </div> </div>

1 0

[community/master] Clean up list of projects to: 1. hide OONI projects for now and 2. move successfully completed projects to "Past projects" section
by gus＠torproject.org 29 Jan '21

29 Jan '21

commit b4f4e3bd44a410f22b0c229e69a8fd4a4f3073fc Author: Pili Guerra <pili(a)piliguerra.com> Date: Thu Jan 28 17:27:41 2021 +0100 Clean up list of projects to: 1. hide OONI projects for now and 2. move successfully completed projects to "Past projects" section --- content/gsoc/cloudflare-captcha-monitoring/contents.lr | 6 +++++- content/gsoc/ooni-explorer-findings/contents.lr | 6 +++++- content/gsoc/ooni-explorer-testing/contents.lr | 2 +- content/gsoc/ooni-probe-desktop-custom-urls/contents.lr | 2 +- content/gsoc/ooni-probe-experiments/contents.lr | 2 +- content/gsoc/privacy-aware-geo-lookup/contents.lr | 2 +- content/gsoc/snowflake-android-proxy/contents.lr | 6 +++++- 7 files changed, 19 insertions(+), 7 deletions(-) diff --git a/content/gsoc/cloudflare-captcha-monitoring/contents.lr b/content/gsoc/cloudflare-captcha-monitoring/contents.lr index eae7c86..b8e3346 100644 --- a/content/gsoc/cloudflare-captcha-monitoring/contents.lr +++ b/content/gsoc/cloudflare-captcha-monitoring/contents.lr @@ -4,7 +4,11 @@ _template: layout.html --- html: two-columns-page.html --- -active: True +active: False +--- +completed: True +--- +url: https://gitlab.torproject.org/woswos/CAPTCHA-Monitor --- section: GSoC --- diff --git a/content/gsoc/ooni-explorer-findings/contents.lr b/content/gsoc/ooni-explorer-findings/contents.lr index 270ccd4..b04887e 100644 --- a/content/gsoc/ooni-explorer-findings/contents.lr +++ b/content/gsoc/ooni-explorer-findings/contents.lr @@ -4,7 +4,11 @@ _template: layout.html --- html: two-columns-page.html --- -active: True +active: False +--- +completed: True +--- +url: https://gist.github.com/kronaemmanuel/ae1ebafa039a3361fb422462109ae035 --- section: GSoC --- diff --git a/content/gsoc/ooni-explorer-testing/contents.lr b/content/gsoc/ooni-explorer-testing/contents.lr index 1345807..121b63d 100644 --- a/content/gsoc/ooni-explorer-testing/contents.lr +++ b/content/gsoc/ooni-explorer-testing/contents.lr @@ -4,7 +4,7 @@ _template: layout.html --- html: two-columns-page.html --- -active: True +active: False --- section: GSoC --- diff --git a/content/gsoc/ooni-probe-desktop-custom-urls/contents.lr b/content/gsoc/ooni-probe-desktop-custom-urls/contents.lr index 6b09396..9b2a6fb 100644 --- a/content/gsoc/ooni-probe-desktop-custom-urls/contents.lr +++ b/content/gsoc/ooni-probe-desktop-custom-urls/contents.lr @@ -4,7 +4,7 @@ _template: layout.html --- html: two-columns-page.html --- -active: True +active: False --- section: GSoC --- diff --git a/content/gsoc/ooni-probe-experiments/contents.lr b/content/gsoc/ooni-probe-experiments/contents.lr index 1eb568e..260474b 100644 --- a/content/gsoc/ooni-probe-experiments/contents.lr +++ b/content/gsoc/ooni-probe-experiments/contents.lr @@ -4,7 +4,7 @@ _template: layout.html --- html: two-columns-page.html --- -active: True +active: False --- section: GSoC --- diff --git a/content/gsoc/privacy-aware-geo-lookup/contents.lr b/content/gsoc/privacy-aware-geo-lookup/contents.lr index e170747..6e9df77 100644 --- a/content/gsoc/privacy-aware-geo-lookup/contents.lr +++ b/content/gsoc/privacy-aware-geo-lookup/contents.lr @@ -4,7 +4,7 @@ _template: layout.html --- html: two-columns-page.html --- -active: True +active: False --- section: GSoC --- diff --git a/content/gsoc/snowflake-android-proxy/contents.lr b/content/gsoc/snowflake-android-proxy/contents.lr index f1a8906..0b188f6 100644 --- a/content/gsoc/snowflake-android-proxy/contents.lr +++ b/content/gsoc/snowflake-android-proxy/contents.lr @@ -4,7 +4,11 @@ _template: layout.html --- html: two-columns-page.html --- -active: True +active: False +--- +completed: True +--- +url: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… --- section: GSoC ---

1 0

[status-site/main] Mark v3 onion and dir auth issue as resolved
by gk＠torproject.org 29 Jan '21

29 Jan '21

commit 02df8c549624ce5cbe1fb96aee92cade9555dece Author: Georg Koppen <gk(a)torproject.org> Date: Fri Jan 29 14:02:58 2021 +0000 Mark v3 onion and dir auth issue as resolved --- content/issues/2021-01-28-dir-auth.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/issues/2021-01-28-dir-auth.md b/content/issues/2021-01-28-dir-auth.md index 64494cd..1db8571 100644 --- a/content/issues/2021-01-28-dir-auth.md +++ b/content/issues/2021-01-28-dir-auth.md @@ -1,7 +1,8 @@ --- title: Disruption of v3 onion services and consensus building date: 2021-01-27 23:00:00 -resolved: false +resolved: true +resolvedWhen: 2021-01-29 05:30:00 # Possible severity levels: down, disrupted, notice severity: disrupted affected:

1 0