Draft
Conversation
- unit-wolfguard and test-wolfguard; - updated documentation; - workflow (non-fips); - minor edits to the esp source and unit tests to be FIPS compliant when running against a wolfssl built in FIPS mode;
gasbytes
force-pushed
the
wolfguard-support
branch
from
07f0d67 to
38e24da
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
STILL WIP, working on refactor it in order to not use linux apis at all, so more bare metal centric, missing support for some l3 capabilities in wolfip. effectively depends on the this pr #70
changes made:
adds wolfguard as a wolfIP link-layer driver, giving every socket on the stack transparent WireGuard-compatible encryption without application changes.
wolfguard (wolfguard.ko) is an ARPHRD_NONE netdev, Layer 3 only, no Ethernet. wolfIP is Layer 2 and expects Ethernet frames.
(temporary behaviour) The driver (wolfip_wolfguard.c) basically implements the logic this by intercepting ARP requests from wolfIP and returning synthetic replies with dummy MACs, then stripping/prepending Ethernet headers on the send/receive path.
The "fake" MACs never appear on the wire; all actual I/O goes through an AF_PACKET/SOCK_DGRAM socket (wolfguard is not a TUN device) carrying raw IP packets that the kernel module encrypts/decrypts transparently: