mirror of
https://github.com/bol-van/zapret.git
synced 2025-08-10 01:02:03 +03:00
update docs
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
# zapret v70.4
|
||||
# zapret v70.5
|
||||
|
||||
# SCAMMER WARNING
|
||||
|
||||
@@ -265,6 +265,12 @@ Fakes are separate generated by nfqws packets carrying false information for DPI
|
||||
|
||||
`--dpi-desync-fooling` takes multiple comma separated values.
|
||||
|
||||
|
||||
Multiple parameters `--dpi-desync-fake-???` are supported except for the `--dpi-desync-fake-syndata`.
|
||||
Fakes are sent in the specified order. `--dpi-desync-repeats` resends each fake.
|
||||
Resulting order would be : `fake1 fake1 fake1 fake2 fake2 fake2 fake3 fake3 fake3 .....`
|
||||
|
||||
|
||||
### FAKE mods
|
||||
|
||||
**nfqws** has built-in TLS fake. It can be customized with `--dpi-desync-fake-tls` option.
|
||||
@@ -282,6 +288,10 @@ It's possible to use TLS Client Hello with any fingerprint and any SNI.
|
||||
By default if custom fake is not defined `rnd,rndsni,dupsid` mods are applied. If defined - `none`.
|
||||
This behaviour is compatible with previous versions with addition of `dupsid`.
|
||||
|
||||
If TLS mod is enabled and there're multiple TLS fakes, all valid TLS Client Hello fakes are modified.
|
||||
If there's no TLS Client Hello program exits with error.
|
||||
|
||||
|
||||
### TCP segmentation
|
||||
|
||||
* `multisplit`. split request at specified in `--dpi-desync-split-pos` positions
|
||||
|
Reference in New Issue
Block a user