Some notes, tools, and techniques for reverse engineering macOS binaries.
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
| http://www.rijksoverheid.nl | |
| http://www.rivm.nl | |
| http://coronadashboard.rijksoverheid.nl | |
| http://www.nederlandwereldwijd.nl | |
| http://www.government.nl | |
| http://lci.rivm.nl | |
| http://www.rvo.nl | |
| http://www.defensie.nl | |
| http://www.werkenvoornederland.nl | |
| http://www.rijkswaterstaat.nl |
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
| # Author: 1ikeadragon, for GAMERANT | |
| param ( | |
| $InputFile = "BlockList.txt", | |
| $RuleName, | |
| $ProfileType = "any", | |
| $InterfaceType = "any" | |
| ) | |
| $file = get-item $InputFile -ErrorAction SilentlyContinue | |
| if (-not $file) { |
When touching any code, configuration, or infrastructure, apply the threat-modelling principles below before making changes. Think attacker-first: assume hostile input, compromised dependencies, and least-privilege as defaults.
Before writing or modifying code, ask:
- What crosses a trust boundary here? (user input → backend, service A → service B, CLI arg → shell, etc.)
- Is data validated and sanitised at the boundary, not deep inside?