Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
rdsys
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
The Tor Project
Anti-censorship
rdsys
Commits
743ae977
Verified
Commit
743ae977
authored
1 year ago
by
shelikhoo
Browse files
Options
Downloads
Patches
Plain Diff
line wrapping adjustmemt for doc/gettor.md
parent
547a476b
No related branches found
No related tags found
1 merge request
!201
Went hunting for gettor strings, found this .md file and did an editing pass on it.
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/gettor.md
+25
-22
25 additions, 22 deletions
doc/gettor.md
with
25 additions
and
22 deletions
doc/gettor.md
+
25
−
22
View file @
743ae977
...
...
@@ -4,12 +4,12 @@ Gettor distributor and updater
The gettor distributor provides links to download Tor Browser
from uncensored providers over email. It is used by users on networks where
the main Tor download website is being blocked, so they can send an email to
gettor and receive a response with a link to download Tor Browser that will
not be
blocked in their network.
gettor and receive a response with a link to download Tor Browser that will
not be
blocked in their network.
It is implemented as a resource in the backend, a distributor that
communicates over email and an updater that uploads the new Tor Browser
releases to
the providers.
communicates over email and an updater that uploads the new Tor Browser
releases to
the providers.
TBLink resource
---------------
...
...
@@ -26,41 +26,44 @@ metadata:
They are different than most other resources in rdsys as they are stored in
disk by rdsys, not partitioned and updated by an updater process.
While most other resources are passively pulled by rdsys kraken service TBLink
resources are updated by an external process (the gettor updater) that sends
the updates to the backend over HTTP requests. They are stored as a json file
While most other resources are passively pulled by rdsys kraken service TBLink
resources are updated by an external process (the gettor updater) that sends
the updates to the backend over HTTP requests. They are stored as a json file
on disk.
TBLink resources are unpartitioned, so each distributor with access to them
TBLink resources are unpartitioned, so each distributor with access to them
gets the full list of resources. There is no need in gettor to assign resources
to unique distributors.
Tor Browser releases might be for some platforms and not others. The backend, distributors.
and updater are designed to provide the latest version for each platform.
Tor Browser releases might be for some platforms and not others. The backend,
distributors. and updater are designed to provide the latest version for
each platform.
Gettor updater
--------------
The gettor updater monitors Tor Browser releases, and when there is a new release
uploads it to all the supported providers (github for now) and sends the new
links to the backend over http to be propagated to the distributors.
The gettor updater monitors Tor Browser releases, and when there is a new
release uploads it to all the supported providers (github for now) and
sends the new links to the backend over http to be propagated to the
distributors.
It does listen to the
[
release
json
](
https://aus1.torproject.org/torbrowser/update_3/release/downloads.json
)
and get the latest version for each platform of the Tor Browser and its
signature to
upload to each provider.
and get the latest version for each platform of the Tor Browser and its
signature to
upload to each provider.
Gettor distributor
------------------
The gettor distributor listens to incoming emails over IMAP and responds with
links to download Tor Browser for the requested platform and language. It does accept
the platform and/or language being provided in the subject or the body of the
email.
If platform is provided the distributor will answer with a help email describing
how to use the service. If the platform is provided but no language is provided it will
send the download links for the requested platform and
*en-US*
language.
links to download Tor Browser for the requested platform and language.
It does accept the platform and/or language being provided in the subject or
the body of the email.
If platform is provided the distributor will answer with a help email
describing how to use the service. If the platform is provided but no language
is provided it will send the download links for the requested platform and
*en-US*
language.
There are three predefined platform aliases:
*
**windows**
. That will provide
*win32*
bundles.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment