[GH-ISSUE #37] [Discussion] Upstream the changes? #19

New issue

Open

opened 2026-10-13 21:05:19 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-13 21:05:19 +00:00

Owner

Originally created by @eternal-sorrow on GitHub (Oct 16, 2024).
Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-linux-kernel-module/issues/37

Is it possible to upstream the changes in AmneziaWG to the mainline WireGuard kernel module? By default keeping full compatibility with normal Wireguard, but by adding some additional parameters one could enable the Amnezia mode, masking the package signatures.

Originally created by @eternal-sorrow on GitHub (Oct 16, 2024). Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-linux-kernel-module/issues/37 Is it possible to upstream the changes in AmneziaWG to the mainline WireGuard kernel module? By default keeping full compatibility with normal Wireguard, but by adding some additional parameters one could enable the Amnezia mode, masking the package signatures.

bsakaguchi commented

2026-10-13 21:05:21 +00:00

Author

Owner

@13xforever commented on GitHub (Jul 6, 2025):

Upstream has rejected multiple proposals to add any kind of obfuscation options to the protocol, it is highly unlikely they'll accept awg changes, considering it's explicitly stated as such in their Known Limitations section.

@13xforever commented on GitHub (Jul 6, 2025): Upstream has rejected multiple proposals to add any kind of obfuscation options to the protocol, it is highly unlikely they'll accept awg changes, considering it's explicitly stated as such in their [Known Limitations](https://www.wireguard.com/known-limitations/) section.

bsakaguchi referenced this issue

2026-10-13 21:07:11 +00:00

[PR #19] [MERGED] Fixed typos in readme #158