summaryrefslogtreecommitdiff
path: root/specs
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2008-09-11 19:56:20 +0000
committerNick Mathewson <nickm@torproject.org>2008-09-11 19:56:20 +0000
commit6dd05e0e0f3a95204fb1f93f433c4d51c3f4459b (patch)
tree3cdd10cb89907a6e53441cbb5952c3f09b1d5ce0 /specs
parentfcd98068a15eabbd3ed9264993c15058fd5c4815 (diff)
More glider spec tweaks.
git-svn-id: file:///home/or/svnrepo/updater/trunk@16854 55e972cd-5a19-0410-ae62-a4d7a52db4cd
Diffstat (limited to 'specs')
-rw-r--r--specs/U2-formats.txt52
1 files changed, 51 insertions, 1 deletions
diff --git a/specs/U2-formats.txt b/specs/U2-formats.txt
index 64add21..476a92a 100644
--- a/specs/U2-formats.txt
+++ b/specs/U2-formats.txt
@@ -370,7 +370,8 @@
(mirrorlist
(ts TIME)
(mirrors
- ( (mirror ({(name N) (urlbase U) (contents PATH+) (ATTR VAL)})) * )
+ ( (mirror ({(name N) (urlbase U) (contents PATH+) (weight W)
+ (official)? (ATTR VAL)})) * )
...
)
@@ -382,6 +383,11 @@
elements are the components describing how much of the packages
directory is mirrored. Their format is as in the keylist file.
+ W is an integer used to weight mirrors when picking at random;
+ mirrors with more bandwidth should have higher weigths. The
+ "official" element should only be present if the mirror is (one of
+ the) official repositories operated by the Tor Project.
+
3.5. File formats: timestamp files
The timestamp file is signed by a timestamp key. It indicates the
@@ -496,6 +502,12 @@
Clients SHOULD cache at least the latest versions they have received
of all files.
+4.1.1. Download preferences
+
+ Users should be able to specify that packages must be only
+ downloaded over Tor, or must only be downloaded over encrypted
+ protocols, or both. Users should also be able to force
+
4.2. Mirrors
Periodically, mirrors do an rsync or equivalent to fetch the latest
@@ -575,3 +587,41 @@
keylist. Note that a new package or bundle key must re-sign and
issue new versions of all packages or bundles it has generated.
+
+
+F. Future directions and open questions
+
+F.1. Package decomposition
+
+ It would be neat to decouple existing packages. Right now, we'd
+ never want a windows user to have to fetch an openssl dll and Tor
+ separately. But if they're using an auto-update tool, it'd be
+ pretty keen to have them not need to fetch a new openssl every time
+ Tor has a bugfix.
+
+F.2. Caching at Tor servers.
+
+ See Tor Proposal number 127.
+
+F.3. Support for more download methods
+
+ Ozymandns, chunked downloads, and bittorrent would all be neat
+ ideas.
+
+
+R. Ideas I'm rejecting for the moment
+
+R.1. Considering recommended versions from Tor consensus directory documents
+
+ This requires a working Tor to update Tor; that's not necessarily a
+ great idea.
+
+R.2. Integration with existing GPG signatures
+
+ The OpenPGP signature and key format is so complicated that you'd
+ have to be mad to touch it.
+
+
+
+
+