Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
O
obfs4-deprecated
Manage
Activity
Members
Labels
Plan
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Analyze
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
leap
obfs4-deprecated
Commits
19f34317
Commit
19f34317
authored
10 years ago
by
Yawning Angel
Browse files
Options
Downloads
Patches
Plain Diff
Change the MSS to 1448 bytes, because timestamps are a thing.
This breaks wireprotocol compatibility.
parent
7c37109c
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/obfs4-spec.txt
+4
-4
4 additions, 4 deletions
doc/obfs4-spec.txt
framing/framing.go
+1
-1
1 addition, 1 deletion
framing/framing.go
with
5 additions
and
5 deletions
doc/obfs4-spec.txt
+
4
−
4
View file @
19f34317
...
...
@@ -89,7 +89,7 @@
2. The client sends a handshake request to the server where:
X' = Elligator 2 representative of X (32 bytes)
P_C = Random padding [87, 13
96
] bytes long
P_C = Random padding [87, 13
84
] bytes long
M_C = HMAC-SHA256-128(B | NODEID, X')
E = String representation of the number of hours since the UNIX
epoch
...
...
@@ -145,7 +145,7 @@
Y' = Elligator 2 Representative of Y (32 bytes)
AUTH = The ntor authentication tag (32 bytes)
P_S = Random padding [0, 13
64
] bytes long
P_S = Random padding [0, 13
52
] bytes long
M_S = HMAC-SHA256-128(B | NODEID, Y')
E' = E from the client request
MAC_S = HMAC-SHA256-128(B | NODEID, Y' | AUTH | P_S | M_S | E')
...
...
@@ -193,7 +193,7 @@
be 0 in which case all the remaining data is authenticated and decrypted,
but ignored.
The maximum allowed frame length is 14
60
bytes, which allows up to 14
39
The maximum allowed frame length is 14
48
bytes, which allows up to 14
27
bytes of useful payload to be transmitted per "frame".
If unsealing a secretbox ever fails (due to a Tag mismatch), implementations
...
...
@@ -228,7 +228,7 @@
part of the serverResponse if it always sends the frame immediately
following the serverResponse body. If implementations chose to do this,
the TYPE_PRNG_SEED frame MUST have 0 bytes of padding, and P_S MUST
consist of [0,1
309
] bytes of random padding.
consist of [0,1
297
] bytes of random padding.
7. References
...
...
This diff is collapsed.
Click to expand it.
framing/framing.go
+
1
−
1
View file @
19f34317
...
...
@@ -70,7 +70,7 @@ import (
const
(
// MaximumSegmentLength is the length of the largest possible segment
// including overhead.
MaximumSegmentLength
=
1500
-
40
MaximumSegmentLength
=
1500
-
(
40
+
12
)
// FrameOverhead is the length of the framing overhead.
FrameOverhead
=
lengthLength
+
secretbox
.
Overhead
...
...
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