mirror of
https://github.com/amnezia-vpn/amneziawg-go.git
synced 2026-10-14 05:41:54 +00:00
[GH-ISSUE #116] Add steganography #63
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
amnezia-vpn/amneziawg-go#63
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @hashelq on GitHub (Feb 17, 2026).
Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-go/issues/116
Originally assigned to: @ygurov on GitHub.
Countries like Turkmenistan already use invasive DPI's that block all non-formalized encrypted (high entropic) connections.
Users from Russia report that local government started detecting VPN traffic (VLESS) using Ai's.
I suggest adding steganographic protection into AWG protocol, allowing mixing the encrypted VPN traffic with non encrypted "looking ok" traffic such as images, videos and low-entropic data. This will make the underlying traffic look more natural.
Another way of implementing that would be to pad the data using pregenerated range series to reduce its entropy and mislead dpi.
@ygurov commented on GitHub (Feb 19, 2026):
Hi
I think entropy question is a common sense here, but are you really sure current DPI/TSPU mechanisms are actually using it?
Have the similar feature in backlog anyways, assigning to myself
@hashelq commented on GitHub (Feb 20, 2026):
Not sure, but I have heard information that Turkmenistan requiring an approved security certificate before using it on public network, otherwise they block the encrypted traffic. Even if thats not the case, ig its still worth implementing that as a fallback in case it gets activated somewhere somehow.
I don't think I know much more.