Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
O
obfs4portscan
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
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
Legacy
gitolite
user
phw
obfs4portscan
Commits
37254249
Unverified
Commit
37254249
authored
5 years ago
by
Philipp Winter
Browse files
Options
Downloads
Patches
Plain Diff
Add instructions and explanations.
parent
873dc9ad
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+17
-1
17 additions, 1 deletion
README.md
with
17 additions
and
1 deletion
README.md
+
17
−
1
View file @
37254249
# obfs4PortScan
Tests if a Tor bridge's obfs4 port is publicly reachable.
This service lets bridge operators test if their bridge's obfs4 port is
publicly reachable.
## Command line arguments arguments
The tool takes as input two command line arguments: a path to a certificate
file and a path to its key file, both in PEM format. We use these files to run
the HTTPS server.
## Scanning method
We try to establish a TCP connection with the given IP address and port using
golang's
`net.DialTimeout`
function. If we don't get a response within three
seconds, we deem the port unreachable. We also deem the port unreachable if we
get a RST segment before the timeout. In both cases, we display the error
message that we got from
`net.DialTimeout`
.
We implement a simple rate limiter that limits incoming requests to an average
of one per second with bursts of as many as five requests per second.
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