This is meant as a supplement to interact with the Windows firewall via COM interfaces.
Yes, of course. @TheRealWover's existing code from Donut a bit of insight in how to implement uuid's functionality without losing sleep. Thank you!
COM in general through lower-level languages is a pain. This was meant to show that we can intermix convenience interfaces with C++ in BOF files.
This shows that it's possible to use C++ classes/wrappers within BOF files, eliminating the need to BEGIN_INTERFACE and lose ourselves to reimplementation depths of despair in straight C.
- Fetching the total number of known Windows firewall rules via:
fw_walk total - Enumerating each of the three default locations for firewalls configurations (profile, domain, and public) via:
fw_walk status - The ability to disable (assuming you have sufficient privileges) all three default firewalls (profile, domian, and public) via:
fw_walk disable - The ability to enable/revert your actions (assuming you have sufficient privileges) all three default firewalls (profile, domain, and public) via:
fw_walk enable
- In this case, you have two options:
- Use the existing, compiled object file, located in the
distdirectory (AKA proceed to major step two) - Compile from source via the
Makefilecd srcmake cleanmake
- Use the existing, compiled object file, located in the
- Load the
Aggressorfile, in theScript Manager, located in thedistdirectory - Within a provided
Beacon,beacon> fw_walkto display the previously-mentioned options
- We're still using the
Win32API andDynamic Function Resolution. This is for you to determine as far as "risk" - You may attempt to incur a privileged action without sufficient requisite permissions. I can't keep you from burning your hand.
The sky's the limit:
- Add a rule for your own application
- Add a rule for an interface of your choosing
- Delete rules at will