tor-commits April 2011

tor-commits@lists.torproject.org

18 participants
883 discussions

r24607: {website} change de/navigation.wmi to utf-8 (website/trunk/de)
by Runa Sandvik 13 Apr '11

13 Apr '11

Author: runa Date: 2011-04-13 10:04:57 +0000 (Wed, 13 Apr 2011) New Revision: 24607 Modified: website/trunk/de/navigation.wmi Log: change de/navigation.wmi to utf-8 Modified: website/trunk/de/navigation.wmi =================================================================== --- website/trunk/de/navigation.wmi 2011-04-13 10:03:01 UTC (rev 24606) +++ website/trunk/de/navigation.wmi 2011-04-13 10:04:57 UTC (rev 24607) @@ -8,7 +8,7 @@ # path link text my @navigation = ( 'index' , 'Startseite', - 'about/overview' , '�ber Tor', + 'about/overview' , 'Über Tor', 'docs/documentation' , 'Dokumentation', 'projects/projects' , 'Projekte', 'press/press' , 'Presse',

1 0

r24606: {website} change docs/de/sidenav.wmi to utf-8 (website/trunk/docs/de)
by Runa Sandvik 13 Apr '11

13 Apr '11

Author: runa Date: 2011-04-13 10:03:01 +0000 (Wed, 13 Apr 2011) New Revision: 24606 Modified: website/trunk/docs/de/sidenav.wmi Log: change docs/de/sidenav.wmi to utf-8 Modified: website/trunk/docs/de/sidenav.wmi =================================================================== --- website/trunk/docs/de/sidenav.wmi 2011-04-13 04:05:49 UTC (rev 24605) +++ website/trunk/docs/de/sidenav.wmi 2011-04-13 10:03:01 UTC (rev 24606) @@ -18,7 +18,7 @@ my $sidenav; $sidenav = [ {'url' => 'docs/documentation', - 'txt' => 'Dokumentations �bersicht', + 'txt' => 'Dokumentations Übersicht', }, { 'url' => 'docs/installguide', @@ -40,14 +40,14 @@ 'txt' => 'Installation auf Maemo/N900', }, {'url' => 'docs/verifying-signatures', - 'txt' => '�berpr�fe unsere GPG Signatur', + 'txt' => 'Überprüfe unsere GPG Signatur', }, {'url' => 'docs/tor-doc-web', 'txt' => 'Richte deinen Browser zur Nutzung von Tor ein', }], }, {'url' => 'docs/manual', - 'txt' => 'Handb�cher', + 'txt' => 'Handbücher', 'subelements' => [ {'url' => 'docs/tor-doc-relay', 'txt' => 'Konfiguration eines Relais', @@ -56,7 +56,7 @@ 'txt' => 'Konfiguration eines versteckten Dienstes', }, {'url' => 'docs/bridges', - 'txt' => 'Konfiguration eines Br�cken Relais', + 'txt' => 'Konfiguration eines Brücken Relais', }, {'url' => 'docs/running-a-mirror', 'txt' => 'Konfiguration eines Spiegelservers', @@ -68,7 +68,7 @@ 'txt' => 'Tor -alpha Handbuch', }, {'url' => 'docs/proxychain', - 'txt' => 'Konfigurieren von Tor f�r die Verwendung eines Proxy Servers', + 'txt' => 'Konfigurieren von Tor für die Verwendung eines Proxy Servers', }], }, {

1 0

[torbrowser/master] 1.3.22 was created with missing langpacks, so all Firefoxes were in English. fix this with 1.3.23. add location of Burmese langpack too.
by erinn＠torproject.org 13 Apr '11

13 Apr '11

commit c79e327fd524572f70b1b4cc8d03856a0fe6cb03 Author: Erinn Clark <erinn(a)torproject.org> Date: Wed Apr 13 06:11:51 2011 +0200 1.3.22 was created with missing langpacks, so all Firefoxes were in English. fix this with 1.3.23. add location of Burmese langpack too. --- README | 8 +++++++- build-scripts/Makefile | 6 ++++-- 2 files changed, 11 insertions(+), 3 deletions(-) diff --git a/README b/README index c631f12..d672ac9 100644 --- a/README +++ b/README @@ -4,7 +4,7 @@ Tor USB project Included applications --------------------- -Vidalia 0.2.10 (with Qt 4.6.2) +Vidalia 0.2.12 (with Qt 4.6.2) Tor 0.2.1.30 (with libevent-1.4.13, zlib-1.2.3 and openssl-0.9.8p) Polipo 1.0.4.1 FirefoxPortable 3.6.16 @@ -334,3 +334,9 @@ Changelog 1.3.21: Released 2011-03-23 Update Firefox to 3.6.16 Update HTTPS-Everywhere to 0.9.9.development.4 + +1.3.22: Released 2011-04-12 + Update Vidalia to 0.2.12 + +1.3.23: Released 2011-04-13 + Fix langpack mistake that made Firefox only use English diff --git a/build-scripts/Makefile b/build-scripts/Makefile index b505df3..61f8ee8 100644 --- a/build-scripts/Makefile +++ b/build-scripts/Makefile @@ -22,7 +22,7 @@ FIREFOX_VERSION=3.6.16 PIDGIN_VERSION=2.7.5 ## Location of bundle components -VIDALIA=/e/build/vidalia-0.2.10 +VIDALIA=/e/build/vidalia-0.2.12 TOR=/e/build/tor-0.2.1.30 POLIPO=/e/build/polipo-1.0.4.1 FIREFOX_SRC=/e/build/FirefoxPortable-$(FIREFOX_VERSION) @@ -49,7 +49,7 @@ DEST="Generic Bundle" NAME="Tor Browser" ## Version and name of the compressed bundle (also used for source) -VERSION=1.3.21 +VERSION=1.3.23 DEFAULT_COMPRESSED_BASENAME=tor-browser- IM_COMPRESSED_BASENAME=tor-im-browser- DEFAULT_COMPRESSED_NAME=$(DEFAULT_COMPRESSED_BASENAME)$(VERSION) @@ -69,6 +69,8 @@ DEFAULT_EXTENSIONS=torbutton.xpi TORBUTTON=https://www.torproject.org/torbutton/releases/torbutton-$(TORBUTT… ## Where to download Mozilla language packs +MY_LANGPACK=http://www.wordpress-my.tk/langpack-firefox-3.6-my.xpi + MOZILLA_LANGUAGE=http://releases.mozilla.org/pub/mozilla.org/firefox/releas… ## Where Farsi Language Pack can be downloaded from

1 0

r24605: {website} revert tbb windows to 1.3.21 until langpack issue is fixed (website/trunk/include)
by Erinn Clark 13 Apr '11

13 Apr '11

Author: erinn Date: 2011-04-13 04:05:49 +0000 (Wed, 13 Apr 2011) New Revision: 24605 Modified: website/trunk/include/versions.wmi Log: revert tbb windows to 1.3.21 until langpack issue is fixed Modified: website/trunk/include/versions.wmi =================================================================== --- website/trunk/include/versions.wmi 2011-04-13 02:17:50 UTC (rev 24604) +++ website/trunk/include/versions.wmi 2011-04-13 04:05:49 UTC (rev 24605) @@ -19,7 +19,7 @@ <define-tag version-osx-ppc-stable whitespace=delete>0.2.1.30</define-tag> <define-tag version-osx-ppc-alpha whitespace=delete>0.2.2.24-alpha</define-tag> -<define-tag version-torbrowserbundle whitespace=delete>1.3.22</define-tag> +<define-tag version-torbrowserbundle whitespace=delete>1.3.21</define-tag> <define-tag version-torbrowser-tor whitespace=delete>0.2.1.30</define-tag> <define-tag version-torbrowser-tor-components whitespace=delete>libevent-1.4.13, zlib-1.2.3, openssl-0.9.8p</define-tag> <define-tag version-torbrowser-firefox whitespace=delete>3.6.16</define-tag> @@ -27,7 +27,7 @@ <define-tag version-torbrowser-polipo whitespace=delete>1.0.4.1</define-tag> <define-tag version-torbrowser-pidgin whitespace=delete>2.7.5</define-tag> <define-tag version-torbrowser-otr whitespace=delete>3.2</define-tag> -<define-tag version-torbrowser-vidalia whitespace=delete>0.2.12</define-tag> +<define-tag version-torbrowser-vidalia whitespace=delete>0.2.10</define-tag> <define-tag version-torimbrowserbundle whitespace=delete>1.3.21</define-tag> <define-tag version-torbrowserbundlelinux32 whitespace=delete>1.1.7</define-tag>

1 0

r24604: {website} update some more vidalia versions (website/trunk/include)
by Erinn Clark 13 Apr '11

13 Apr '11

Author: erinn Date: 2011-04-13 02:17:50 +0000 (Wed, 13 Apr 2011) New Revision: 24604 Modified: website/trunk/include/versions.wmi Log: update some more vidalia versions Modified: website/trunk/include/versions.wmi =================================================================== --- website/trunk/include/versions.wmi 2011-04-13 02:09:32 UTC (rev 24603) +++ website/trunk/include/versions.wmi 2011-04-13 02:17:50 UTC (rev 24604) @@ -56,9 +56,9 @@ <define-tag package-win32-stable whitespace=delete>/dist/win32/tor-<version-win32-stable>-win32.exe</define-tag> <define-tag package-win32-alpha whitespace=delete>/dist/win32/tor-<version-win32-alpha>-win32.exe</define-tag> -<define-tag file-win32-bundle-stable whitespace=delete>vidalia-bundle-<version-win32-bundle-stable>-0.2.10.exe</define-tag> +<define-tag file-win32-bundle-stable whitespace=delete>vidalia-bundle-<version-win32-bundle-stable>-0.2.12.exe</define-tag> <define-tag package-win32-bundle-stable whitespace=delete>/dist/vidalia-bundles/<file-win32-bundle-stable></define-tag> -<define-tag file-win32-bundle-alpha whitespace=delete>vidalia-bundle-<version-win32-bundle-alpha>-0.2.10.exe</define-tag> +<define-tag file-win32-bundle-alpha whitespace=delete>vidalia-bundle-<version-win32-bundle-alpha>-0.2.12.exe</define-tag> <define-tag package-win32-bundle-alpha whitespace=delete>/dist/vidalia-bundles/<file-win32-bundle-alpha></define-tag> <define-tag file-osx-x86-bundle-stable whitespace=delete>vidalia-bundle-<version-osx-x86-bundle-stable>-0.2.12-i386.dmg</define-tag>

1 0

r24603: {website} bump the tor version for website builds. (website/trunk)
by Andrew Lewman 13 Apr '11

13 Apr '11

Author: phobos Date: 2011-04-13 02:09:32 +0000 (Wed, 13 Apr 2011) New Revision: 24603 Modified: website/trunk/Makefile Log: bump the tor version for website builds. Modified: website/trunk/Makefile =================================================================== --- website/trunk/Makefile 2011-04-13 01:43:57 UTC (rev 24602) +++ website/trunk/Makefile 2011-04-13 02:09:32 UTC (rev 24603) @@ -11,8 +11,8 @@ # 5. ./publish export TORGIT=/home/runa/dev/tor/.git -export STABLETAG=tor-0.2.2.23-alpha -export DEVTAG=tor-0.2.2.23-alpha +export STABLETAG=tor-0.2.2.24-alpha +export DEVTAG=tor-0.2.2.24-alpha WMLBASE=. SUBDIRS=docs eff projects press about download getinvolved donate torbutton

1 0

r24602: {website} it is time for the new tor 0.2.2.24-alpha and vidalia 0.2.12 (website/trunk/include)
by Erinn Clark 13 Apr '11

13 Apr '11

Author: erinn Date: 2011-04-13 01:43:57 +0000 (Wed, 13 Apr 2011) New Revision: 24602 Modified: website/trunk/include/versions.wmi Log: it is time for the new tor 0.2.2.24-alpha and vidalia 0.2.12 releases Modified: website/trunk/include/versions.wmi =================================================================== --- website/trunk/include/versions.wmi 2011-04-12 18:15:12 UTC (rev 24601) +++ website/trunk/include/versions.wmi 2011-04-13 01:43:57 UTC (rev 24602) @@ -1,25 +1,25 @@ <define-tag version-stable whitespace=delete>0.2.1.30</define-tag> -<define-tag version-alpha whitespace=delete>0.2.2.23-alpha</define-tag> +<define-tag version-alpha whitespace=delete>0.2.2.24-alpha</define-tag> <define-tag version-win32-stable whitespace=delete>0.2.1.30</define-tag> -<define-tag version-win32-alpha whitespace=delete>0.2.2.23-alpha</define-tag> +<define-tag version-win32-alpha whitespace=delete>0.2.2.24-alpha</define-tag> <define-tag version-win32-bundle-stable whitespace=delete>0.2.1.30</define-tag> -<define-tag version-win32-bundle-alpha whitespace=delete>0.2.2.23-alpha</define-tag> +<define-tag version-win32-bundle-alpha whitespace=delete>0.2.2.24-alpha</define-tag> <define-tag version-osx-x86-bundle-stable whitespace=delete>0.2.1.30</define-tag> -<define-tag version-osx-x86-bundle-alpha whitespace=delete>0.2.2.23-alpha</define-tag> +<define-tag version-osx-x86-bundle-alpha whitespace=delete>0.2.2.24-alpha</define-tag> <define-tag version-osx-ppc-bundle-stable whitespace=delete>0.2.1.30</define-tag> -<define-tag version-osx-ppc-bundle-alpha whitespace=delete>0.2.2.23-alpha</define-tag> +<define-tag version-osx-ppc-bundle-alpha whitespace=delete>0.2.2.24-alpha</define-tag> <define-tag version-osx-x86-stable whitespace=delete>0.2.1.30</define-tag> -<define-tag version-osx-x86-alpha whitespace=delete>0.2.2.23-alpha</define-tag> +<define-tag version-osx-x86-alpha whitespace=delete>0.2.2.24-alpha</define-tag> <define-tag version-osx-ppc-stable whitespace=delete>0.2.1.30</define-tag> -<define-tag version-osx-ppc-alpha whitespace=delete>0.2.2.23-alpha</define-tag> +<define-tag version-osx-ppc-alpha whitespace=delete>0.2.2.24-alpha</define-tag> -<define-tag version-torbrowserbundle whitespace=delete>1.3.21</define-tag> +<define-tag version-torbrowserbundle whitespace=delete>1.3.22</define-tag> <define-tag version-torbrowser-tor whitespace=delete>0.2.1.30</define-tag> <define-tag version-torbrowser-tor-components whitespace=delete>libevent-1.4.13, zlib-1.2.3, openssl-0.9.8p</define-tag> <define-tag version-torbrowser-firefox whitespace=delete>3.6.16</define-tag> @@ -27,25 +27,25 @@ <define-tag version-torbrowser-polipo whitespace=delete>1.0.4.1</define-tag> <define-tag version-torbrowser-pidgin whitespace=delete>2.7.5</define-tag> <define-tag version-torbrowser-otr whitespace=delete>3.2</define-tag> -<define-tag version-torbrowser-vidalia whitespace=delete>0.2.10</define-tag> +<define-tag version-torbrowser-vidalia whitespace=delete>0.2.12</define-tag> <define-tag version-torimbrowserbundle whitespace=delete>1.3.21</define-tag> -<define-tag version-torbrowserbundlelinux32 whitespace=delete>1.1.6</define-tag> -<define-tag version-torbrowserbundlelinux64 whitespace=delete>1.1.6</define-tag> -<define-tag version-gnu-torbrowser-tor whitespace=delete>0.2.2.23-alpha</define-tag> +<define-tag version-torbrowserbundlelinux32 whitespace=delete>1.1.7</define-tag> +<define-tag version-torbrowserbundlelinux64 whitespace=delete>1.1.</define-tag> +<define-tag version-gnu-torbrowser-tor whitespace=delete>0.2.2.24-alpha</define-tag> <define-tag version-gnu-torbrowser-tor-components whitespace=delete>libevent-2.0.10, zlib-1.2.3, openssl-0.9.8p</define-tag> <define-tag version-gnu-torbrowser-firefox whitespace=delete>3.6.16</define-tag> <define-tag version-gnu-torbrowser-torbutton whitespace=delete>1.2.5</define-tag> -<define-tag version-gnu-torbrowser-vidalia whitespace=delete>0.2.10</define-tag> +<define-tag version-gnu-torbrowser-vidalia whitespace=delete>0.2.12</define-tag> -<define-tag version-torbrowserbundleosx whitespace=delete>1.0.14</define-tag> -<define-tag version-osx-torbrowser-tor whitespace=delete>0.2.2.23-alpha</define-tag> +<define-tag version-torbrowserbundleosx whitespace=delete>1.0.15</define-tag> +<define-tag version-osx-torbrowser-tor whitespace=delete>0.2.2.24-alpha</define-tag> <define-tag version-osx-torbrowser-firefox whitespace=delete>3.6.16</define-tag> <define-tag version-osx-torbrowser-torbutton whitespace=delete>1.2.5</define-tag> <define-tag version-osx-torbrowser-polipo whitespace=delete>1.0.4.1</define-tag> -<define-tag version-osx-torbrowser-vidalia whitespace=delete>0.2.10</define-tag> +<define-tag version-osx-torbrowser-vidalia whitespace=delete>0.2.12</define-tag> -<define-tag version-vidalia-stable whitespace=delete>0.2.10</define-tag> +<define-tag version-vidalia-stable whitespace=delete>0.2.12</define-tag> <define-tag version-androidbundle-tor whitespace=delete>0.2.2.22-alpha</define-tag> <define-tag version-androidbundle-orbot whitespace=delete>1.0.4.1</define-tag> @@ -61,13 +61,13 @@ <define-tag file-win32-bundle-alpha whitespace=delete>vidalia-bundle-<version-win32-bundle-alpha>-0.2.10.exe</define-tag> <define-tag package-win32-bundle-alpha whitespace=delete>/dist/vidalia-bundles/<file-win32-bundle-alpha></define-tag> -<define-tag file-osx-x86-bundle-stable whitespace=delete>vidalia-bundle-<version-osx-x86-bundle-stable>-0.2.10-i386.dmg</define-tag> +<define-tag file-osx-x86-bundle-stable whitespace=delete>vidalia-bundle-<version-osx-x86-bundle-stable>-0.2.12-i386.dmg</define-tag> <define-tag package-osx-x86-bundle-stable whitespace=delete>/dist/vidalia-bundles/<file-osx-x86-bundle-stable></define-tag> -<define-tag file-osx-x86-bundle-alpha whitespace=delete>vidalia-bundle-<version-osx-x86-bundle-alpha>-0.2.10-i386.dmg</define-tag> +<define-tag file-osx-x86-bundle-alpha whitespace=delete>vidalia-bundle-<version-osx-x86-bundle-alpha>-0.2.12-i386.dmg</define-tag> <define-tag package-osx-x86-bundle-alpha whitespace=delete>/dist/vidalia-bundles/<file-osx-x86-bundle-alpha></define-tag> -<define-tag package-osx-ppc-bundle-stable whitespace=delete>/dist/vidalia-bundles/vidalia-bundle-<version-osx-ppc-bundle-stable>-0.2.10-ppc.dmg</define-tag> -<define-tag package-osx-ppc-bundle-alpha whitespace=delete>/dist/vidalia-bundles/vidalia-bundle-<version-osx-ppc-bundle-alpha>-0.2.10-ppc.dmg</define-tag> +<define-tag package-osx-ppc-bundle-stable whitespace=delete>/dist/vidalia-bundles/vidalia-bundle-<version-osx-ppc-bundle-stable>-0.2.12-ppc.dmg</define-tag> +<define-tag package-osx-ppc-bundle-alpha whitespace=delete>/dist/vidalia-bundles/vidalia-bundle-<version-osx-ppc-bundle-alpha>-0.2.12-ppc.dmg</define-tag> <define-tag package-osx-x86-stable whitespace=delete>/dist/osx-x86/Tor-<version-osx-stable>-i386-Bundle.dmg</define-tag> <define-tag package-osx-x86-alpha whitespace=delete>/dist/osx-x86/Tor-<version-osx-alpha>-i386-Bundle.dmg</define-tag>

1 0

[vidalia/master] Bump development version to 0.2.13-git
by chiiph＠torproject.org 13 Apr '11

13 Apr '11

commit dc1e6b513b3c83c153b6c7228e47ab2358bfc621 Author: Tomas Touceda <chiiph(a)gentoo.org> Date: Sun Apr 10 20:49:24 2011 -0300 Bump development version to 0.2.13-git --- CMakeLists.txt | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/CMakeLists.txt b/CMakeLists.txt index 03c6b5f..b580959 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -13,8 +13,8 @@ set(VER_MAJOR "0") set(VER_MINOR "2") -set(VER_PATCH "12") -set(VERSION "${VER_MAJOR}.${VER_MINOR}.${VER_PATCH}") +set(VER_PATCH "13") +set(VERSION "${VER_MAJOR}.${VER_MINOR}.${VER_PATCH}-git") message(STATUS "Configuring Vidalia ${VERSION}") project(Vidalia)

1 0

[bridgedb/master] Respond to Nick's comments.
by karsten＠torproject.org 12 Apr '11

12 Apr '11

commit e3b46883f593271829787f42d123d9fc3bc13f33 Author: Karsten Loesing <karsten.loesing(a)gmx.net> Date: Tue Apr 12 10:19:18 2011 +0200 Respond to Nick's comments. --- bridge-db-spec.txt | 82 +++++++++++++++++----------------------------------- 1 files changed, 27 insertions(+), 55 deletions(-) diff --git a/bridge-db-spec.txt b/bridge-db-spec.txt index 48a9590..89f0e5c 100644 --- a/bridge-db-spec.txt +++ b/bridge-db-spec.txt @@ -41,15 +41,8 @@ BridgeDB parses the identity from the "r" line and the assigned flags from the "s" line. - BridgeDB MUST discard all bridges that do not have the Running flag. -# I don't think that "discard" is the right word here: we don't actually -# seem to "Forget they exist". Instead, we remember that they are not -# running. (See how parseStatusFile yields a flag that says if the bridges -# are running, and how Main.load sets the bridge's status to running or -# non-running appropriately before passing it to splitter. At no point here -# does a non-running bridge get "discarded", sfaict). -NM - BridgeDB memorizes all remaining bridges as the set of running bridges - that can be given out to bridge users. + BridgeDB memorizes all bridges that have the Running flag as the set of + running bridges that can be given out to bridge users. BridgeDB SHOULD memorize assigned flags if it wants to ensure that sets of bridges given out SHOULD contain at least a given number of bridges with these flags. @@ -58,6 +51,12 @@ BridgeDB learns about a bridge's most recent IP address and OR port from parsing bridge descriptors. + In theory, both IP address and OR port of a bridge are also contained + in the "r" line of the bridge network status, so there is no mandatory + reason for parsing bridge descriptors. But this functionality is still + implemented in case we need information from the bridge descriptor in + the future. + Bridge descriptor files MAY contain one or more bridge descriptors. We expect bridge descriptor to contain at least the following lines in the stated order: @@ -68,45 +67,20 @@ BridgeDB parses the purpose, IP, ORPort, and fingerprint from these lines. - BridgeDB MUST discard bridge descriptors if the fingerprint is not - contained in the bridge network status parsed before or if the bridge - does not have the Running flag. -# See comment above -NM - BridgeDB MAY discard bridge descriptors which have a different purpose - than "bridge". -# "MAY" isn't good enough; we need to know whether it's safe to give -# bridgedb a list of non-bridge-purpose descriptors or not. If it -# discards them, then you shouldn't give bridgedb non-bridge descriptors -# if you _do_ want them handed out. If it doesn't discard them, then you -# shouldn't give bridgedb non-bridge descriptors _unless_ you want them -# handed out. + BridgeDB skips bridge descriptors if the fingerprint is not contained + in the bridge network status parsed before or if the bridge does not + have the Running flag. + BridgeDB discards bridge descriptors which have a different purpose + than "bridge". BridgeDB can be configured to only accept descriptors + with another purpose or not discard descriptors based on purpose at + all. BridgeDB memorizes the IP addresses and OR ports of the remaining bridges. If there is more than one bridge descriptor with the same fingerprint, BridgeDB memorizes the IP address and OR port of the most recently parsed bridge descriptor. -# I confirmed that BridgeDB simply assumes that descriptors in the bridge -# descriptor files are in chronological order and that descriptors in -# cached-descriptors.new are newer than those in cached-descriptors. If -# this is not the case, BridgeDB overwrites a bridge's IP address and OR -# port with those from an older descriptor! I think that the current -# cached-descriptors* files that Tor produces always have descriptors in -# chronological order. But what if we change that, e.g., when trying to -# limit the number of descriptors that Tor memorizes. Should we make the -# assumption that descriptors are ordered chronologically, or should we -# specify that we have to check that explicitly and fix BridgeDB to do -# that? We could also look at the bridge descriptor that is referenced -# from the bridge network status by its descriptor identifier, even though -# that would require us to calculate the descriptor hash. -KL -# We should just look at the 'published' dates in the bridges. Call this a bug, -# I'd say. -NM If BridgeDB does not find a bridge descriptor for a bridge contained in the bridge network status parsed before, it MUST discard that bridge. -# I confirmed that BridgeDB discards (or at least doesn't use) bridges for -# which it doesn't have a bridge descriptor. What's the reason for -# parsing bridge descriptors anyway? Can't we learn a bridge's IP address -# and OR port from the "r" line, too? -KL -# I forget. -NM 2. Assigning bridges to distributors @@ -114,22 +88,19 @@ given) to clients. The current distributors are "email", "https", and "unallocated". - BridgeDB assigns bridges to distributors on a probabilistic basis and - makes these assignments persistent. -# Not exactly probabilistic: it's based on an HMAC hash of the bridge's ID -# and a secret. -NM - Persistence is achieved by using a database to map node ID to distributor. + BridgeDB assigns bridges to distributors based on an HMAC hash of the + bridge's ID and a secret and makes these assignments persistent. + Persistence is achieved by using a database to map node ID to + distributor. Each bridge is assigned to exactly one distributor (including the "unallocated" distributor). BridgeDB MAY be configured to support only a non-empty subset of the distributors specified in this document. BridgeDB MAY define different probabilities for assigning new bridges to distributors. - BridgeDB MUST NOT change existing assignments of bridges to + BridgeDB does not change existing assignments of bridges to distributors, even if probabilities for assigning bridges to distributors change or distributors are disabled entirely. -# Why "MUST NOT" here? This seems like a potentially desirable feature. -# "Does not" would be more accurate. -MN 3. Giving out bridges upon requests @@ -215,12 +186,12 @@ might not process correctly. BridgeDB MUST reject email addresses coming from other domains than a configured set of permitted domains. - BridgeDB SHOULD normalize email addresses by removing "." characters and - by removing parts after the first "+" character. + BridgeDB SHOULD normalize email addresses by removing "." characters + and by removing parts after the first "+" character. BridgeDB MAY discard requests that do not have the value "pass" in their X-DKIM-Authentication-Result header or does not have this header. -# This means in practice that the incoming mail stack needs to check DKIM -# authentication and set X-DKIM-Authentication-Result. + The X-DKIM-Authentication-Result header is set by the incoming mail + stack that needs to check DKIM authentication. BridgeDB SHOULD NOT return a new set of bridges to the same email address until a given time period (typically a few hours) has passed. # Why don't we fix the bridges we give out for a global 3-hour time period @@ -230,12 +201,13 @@ # time values, then people get new bridges when bridges show up, as # opposed to then we decide to reset the bridges we give them. (Yes, this # problem exists for the IP distributor). -NM +# I'm afraid I don't fully understand what you mean here. -KL BridgeDB MAY include bridge fingerprints in replies along with bridge IP addresses and OR ports. BridgeDB SHOULD periodically discard old email-address-to-bridge mappings. - BridgeDB SHOULD reject too many email requires too frequently from the - same normalized address. + BridgeDB SHOULD reject too frequent email requests coming from the same + normalized address. To map previously unseen email addresses to a set of bridges, BridgeDB proceeds as follows:

1 0

[bridgedb/master] Add two sentences from the old proposal idea.
by karsten＠torproject.org 12 Apr '11

12 Apr '11

commit 2254335a591cf15e4759378887e9dbb7b22fbccb Author: Karsten Loesing <karsten.loesing(a)gmx.net> Date: Tue Apr 12 11:20:01 2011 +0200 Add two sentences from the old proposal idea. --- bridge-db-spec.txt | 10 ++++++++++ 1 files changed, 10 insertions(+), 0 deletions(-) diff --git a/bridge-db-spec.txt b/bridge-db-spec.txt index 9c64e37..a90b934 100644 --- a/bridge-db-spec.txt +++ b/bridge-db-spec.txt @@ -121,6 +121,11 @@ BridgeDB may be configured to support one or more distributors that gives out bridges based on the requestor's IP address. Currently, this is how the HTTPS distributor works. + The goal is to avoid handing out all the bridges to users in a similar + IP space and time. +# Someone else should look at proposals/ideas/old/xxx-bridge-disbursement +# to see if this section is missing relevant pieces from it. -KL + BridgeDB fixes the set of bridges to be returned for a defined time period. BridgeDB considers two IP addresses coming from the same /24 as the @@ -179,6 +184,11 @@ BridgeDB can be configured to support one or more distributors that are giving out bridges based on the requestor's email address. Currently, this is how the email distributor works. + The goal is to bootstrap based on one or more popular email service's + sybil prevention algorithms. +# Someone else should look at proposals/ideas/old/xxx-bridge-disbursement +# to see if this section is missing relevant pieces from it. -KL + BridgeDB rejects email addresses containing other characters than the ones that RFC2822 allows. BridgeDB may be configured to reject email addresses containing other

1 0

← Newer
1
...
57
58
59
60
61
62
63
...
89
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits April 2011