Security tooling and systems code

I build what stands between attackers and their target.

I'm DRG, a developer specializing in high-performance code, memory safety and exploit mitigation.

See the work GitHub: drg-src

visitor@drg-src: ~ it works - type help

visitor@drg-src:~$ whoami

visitor

visitor@drg-src:~$ help

about who I am

work projects (cat NAME)

tools languages and tools

contact where to find me

clear clear the screen

~/work

What I have built so far.

danfoss-shield

Open source, MIT Python 3.9+ Linux gateway It finds exposed Danfoss and Dixell refrigeration controllers on a network you own. On the gateway in front of them, it blocks new connections to them from the internet.

How I built it

  • It refuses a public target until you confirm that you are allowed to test it.
  • It backs up the firewall rules first, and one command rolls everything back.
  • It only uses the Python standard library, so there is nothing to install with pip.
  • Tested in CI on Linux (Python 3.9 to 3.14) and on Windows.

How to run it

# Scan a range you own:
./danfoss_shield.py scan 192.168.1.0/24

# Block what you found, dry-run first:
sudo ./danfoss_shield.py fix --all 192.168.1.0/24 --wan eth0 --dry-run

# Undo everything:
sudo ./danfoss_shield.py fix --rollback

Exit codes

CodeMeaning
0Finished. As far as it could tell, nothing is left open
1Could not finish, or something failed. Treat the result as unknown, not as safe
2Controllers with an open auth endpoint found
3Not root for a command that needs it, or Python too old

Handy in cron and CI. Exit 0 still does not prove that the controllers are safe.

~/about

Who I am.

I look at a system the way an attacker would, and then I close what I find.

What I do

To defend something well I have to think like the person breaking in.

Why danfoss-shield

Refrigeration controllers were sitting on the internet with their auth endpoint open, and at the time the vendor patches were not out yet. I did not want to wait, so I wrote the stopgap.

How I build

I want every tool of mine to behave the way danfoss-shield does: careful with what it touches, and honest when it is not sure instead of calling it safe.

Check it yourself

Do not take my word for any of this. The code is public and the tests run in the open, so you can read every line.

~/tools

What I work with.

languages
  • C++
  • C#
  • JavaScript
  • Perl
  • Python
  • Bash
tools
  • Frida
  • YARA
  • XDP
  • Sentinel
  • Node.js
focus
  • Cyber security
  • system optimization

~/contact

Find me on GitHub.

github.com/drg-src

I read the issues and pull requests. If you find a security problem in one of my tools, please follow the SECURITY file in its repository.