Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Tor
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
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
orbea
Tor
Commits
94847ceb
Commit
94847ceb
authored
17 years ago
by
Paul Syverson
Browse files
Options
Downloads
Patches
Plain Diff
Minor edits suggested by Susan Landau
svn:r10686
parent
c045c890
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/design-paper/sptor.tex
+9
-7
9 additions, 7 deletions
doc/design-paper/sptor.tex
with
9 additions
and
7 deletions
doc/design-paper/sptor.tex
+
9
−
7
View file @
94847ceb
...
...
@@ -71,20 +71,22 @@ logical or physical locations to those sites or to observers. It
enables hosts to be publicly accessible yet have similar protection
against location through its
\emph
{
location-hidden services
}
.
To connect to a remote server via Tor
,
the client software learns
To connect to a remote server via Tor the client software
first
learns
a
%signed
list of Tor nodes from several central
\emph
{
directory servers
}
via a
voting protocol to avoid dependence on or complete trust in any one of
them, and incrementally creates a private pathway or
\emph
{
circuit
}
of
encrypted connections through authenticated Tor nodes on the network
whose public keys were obtained form the directory servers,
negotiating a separate set of encryption keys for each hop along the
voting protocol (to avoid dependence on or complete trust in any one
of these servers). It then incrementally creates a private pathway or
\emph
{
circuit
}
across the network. This circuit consists of
encrypted connections through authenticated Tor nodes
whose public keys were obtained from the directory servers. The client
software negotiates a separate set of encryption keys for each hop along the
circuit. The nodes in the circuit are chosen at random by the client
subject to a preference for higher performing nodes to allocate
resources effectively and with a client-chosen preferred set of first
nodes called
\emph
{
entry guards
}
to complicate profiling attacks by
internal adversaries~
\cite
{
hs-attack
}
.
The circuit is extended one node at a time, and each node
The circuit is extended one node at a time, tunneling extensions
through already established portions of the circuit, and each node
along the way knows only the immediately previous and following nodes
in the circuit, so no individual Tor node knows the complete path that
each fixed-sized data packet (or
\emph
{
cell
}
) will take. Thus,
...
...
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