[or-cvs] r12677: make a new 'ideas' subdir for half-baked proposals. make a n (in tor/trunk/doc/spec/proposals: . ideas)
arma at seul.org
arma at seul.org
Wed Dec 5 06:00:03 UTC 2007
Author: arma
Date: 2007-12-05 01:00:03 -0500 (Wed, 05 Dec 2007)
New Revision: 12677
Added:
tor/trunk/doc/spec/proposals/ideas/
tor/trunk/doc/spec/proposals/ideas/xxx-auto-update.txt
Removed:
tor/trunk/doc/spec/proposals/xxx-auto-update.txt
Modified:
tor/trunk/doc/spec/proposals/000-index.txt
tor/trunk/doc/spec/proposals/127-dirport-mirrors-downloads.txt
tor/trunk/doc/spec/proposals/128-bridge-families.txt
tor/trunk/doc/spec/proposals/reindex.pl
Log:
make a new 'ideas' subdir for half-baked proposals.
make a new 'draft' status for nearly-baked proposals.
Modified: tor/trunk/doc/spec/proposals/000-index.txt
===================================================================
--- tor/trunk/doc/spec/proposals/000-index.txt 2007-12-05 05:57:52 UTC (rev 12676)
+++ tor/trunk/doc/spec/proposals/000-index.txt 2007-12-05 06:00:03 UTC (rev 12677)
@@ -49,8 +49,8 @@
124 Blocking resistant TLS certificate usage [ACCEPTED]
125 Behavior for bridge users, bridge relays, and bridge authorities [OPEN]
126 Getting GeoIP data and publishing usage summaries [OPEN]
-127 Relaying dirport requests to Tor download site [NEEDS-RESEARCH]
-128 Families of private bridges [NEEDS-RESEARCH]
+127 Relaying dirport requests to Tor download site / website [DRAFT]
+128 Families of private bridges [DRAFT]
Proposals by status:
@@ -72,8 +72,6 @@
124 Blocking resistant TLS certificate usage
NEEDS-RESEARCH:
118 Advertising multiple ORPorts at once
- 127 Relaying dirport requests to Tor download site
- 128 Families of private bridges
META:
000 Index of Tor Proposals
001 The Tor Proposal Process
@@ -96,3 +94,6 @@
112 Bring Back Pathlen Coin Weight
DEAD:
100 Tor Unreliable Datagram Extension Proposal
+ DRAFT:
+ 127 Relaying dirport requests to Tor download site / website
+ 128 Families of private bridges
Modified: tor/trunk/doc/spec/proposals/127-dirport-mirrors-downloads.txt
===================================================================
--- tor/trunk/doc/spec/proposals/127-dirport-mirrors-downloads.txt 2007-12-05 05:57:52 UTC (rev 12676)
+++ tor/trunk/doc/spec/proposals/127-dirport-mirrors-downloads.txt 2007-12-05 06:00:03 UTC (rev 12677)
@@ -4,7 +4,7 @@
Last-Modified: $Date$
Author: Roger Dingledine
Created: 2007-12-02
-Status: Needs-Research
+Status: Draft
1. Overview
Modified: tor/trunk/doc/spec/proposals/128-bridge-families.txt
===================================================================
--- tor/trunk/doc/spec/proposals/128-bridge-families.txt 2007-12-05 05:57:52 UTC (rev 12676)
+++ tor/trunk/doc/spec/proposals/128-bridge-families.txt 2007-12-05 06:00:03 UTC (rev 12677)
@@ -4,7 +4,7 @@
Last-Modified: $Date$
Author: Roger Dingledine
Created: 2007-12-xx
-Status: Needs-Research
+Status: Draft
1. Overview
Copied: tor/trunk/doc/spec/proposals/ideas/xxx-auto-update.txt (from rev 12676, tor/trunk/doc/spec/proposals/xxx-auto-update.txt)
===================================================================
--- tor/trunk/doc/spec/proposals/ideas/xxx-auto-update.txt (rev 0)
+++ tor/trunk/doc/spec/proposals/ideas/xxx-auto-update.txt 2007-12-05 06:00:03 UTC (rev 12677)
@@ -0,0 +1,39 @@
+
+Notes on an auto updater:
+
+steve wants a "latest" symlink so he can always just fetch that.
+
+roger worries that this will exacerbate the "what version are you
+using?" "latest." problem.
+
+weasel suggests putting the latest recommended version in dns. then
+we don't have to hit the website. it's got caching, it's lightweight,
+it scales. just put it in a TXT record or something.
+
+but, no dnssec.
+
+roger suggests a file on the https website that lists the latest
+recommended version (or filename or url or something like that).
+
+(steve seems to already be doing this with xerobank. he additionally
+suggests a little blurb that can be displayed to the user to describe
+what's new.)
+
+how to verify you're getting the right file?
+a) it's https.
+b) ship with a signing key, and use some openssl functions to verify.
+c) both
+
+andrew reminds us that we have a "recommended versions" line in the
+consensus directory already.
+
+if only we had some way to point out the "latest stable recommendation"
+from this list. we could list it first, or something.
+
+the recommended versions line also doesn't take into account which
+packages are available -- e.g. on Windows one version might be the best
+available, and on OS X it might be a different one.
+
+aren't there existing solutions to this? surely there is a beautiful,
+efficient, crypto-correct auto updater lib out there. even for windows.
+
Modified: tor/trunk/doc/spec/proposals/reindex.pl
===================================================================
--- tor/trunk/doc/spec/proposals/reindex.pl 2007-12-05 05:57:52 UTC (rev 12676)
+++ tor/trunk/doc/spec/proposals/reindex.pl 2007-12-05 06:00:03 UTC (rev 12677)
@@ -15,7 +15,7 @@
my %status = ();
my @KNOWN_STATUSES = qw{
- OPEN ACCEPTED NEEDS-RESEARCH META FINISHED CLOSED SUPERSEDED DEAD};
+ OPEN ACCEPTED NEEDS-RESEARCH META FINISHED CLOSED SUPERSEDED DEAD DRAFT};
for my $f (@files) {
my $num = substr($f, 0, 3);
Deleted: tor/trunk/doc/spec/proposals/xxx-auto-update.txt
===================================================================
--- tor/trunk/doc/spec/proposals/xxx-auto-update.txt 2007-12-05 05:57:52 UTC (rev 12676)
+++ tor/trunk/doc/spec/proposals/xxx-auto-update.txt 2007-12-05 06:00:03 UTC (rev 12677)
@@ -1,39 +0,0 @@
-
-Notes on an auto updater:
-
-steve wants a "latest" symlink so he can always just fetch that.
-
-roger worries that this will exacerbate the "what version are you
-using?" "latest." problem.
-
-weasel suggests putting the latest recommended version in dns. then
-we don't have to hit the website. it's got caching, it's lightweight,
-it scales. just put it in a TXT record or something.
-
-but, no dnssec.
-
-roger suggests a file on the https website that lists the latest
-recommended version (or filename or url or something like that).
-
-(steve seems to already be doing this with xerobank. he additionally
-suggests a little blurb that can be displayed to the user to describe
-what's new.)
-
-how to verify you're getting the right file?
-a) it's https.
-b) ship with a signing key, and use some openssl functions to verify.
-c) both
-
-andrew reminds us that we have a "recommended versions" line in the
-consensus directory already.
-
-if only we had some way to point out the "latest stable recommendation"
-from this list. we could list it first, or something.
-
-the recommended versions line also doesn't take into account which
-packages are available -- e.g. on Windows one version might be the best
-available, and on OS X it might be a different one.
-
-aren't there existing solutions to this? surely there is a beautiful,
-efficient, crypto-correct auto updater lib out there. even for windows.
-
More information about the tor-commits
mailing list